I have a rule that uses a date/time variable as it's trigger...
but this is the result...
Is there a possible bug? Maybe a DST issue?
Is there a possible bug? Maybe a DST issue?
Maybe... What behaviour are you seeing, is the rule triggering at incorrect times? That align with the Daylight Saving differences, like you suspect?
It runs at the scheduled job time in the screenshot exactly 1hr after the time set in the variable. This is the first time I've used this rule since DST went into effect. It did work correctly before.
Looks like it's a known issue that will go away if the powers that be will just do away with DST.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
