You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using @at <datetime> expression, timezone is set twice. The first one is set in the expression itself, the second one is set in the job field. It'd be more logical and consistent to set up timezone only once. My suggestion is:
@at <datetime> should use RFC3339 without timezone like in civil.DateTime.
@at <datetime> should take into account the value of the job timezone field, like any other expressions.
The text was updated successfully, but these errors were encountered:
When using
@at <datetime>
expression, timezone is set twice. The first one is set in the expression itself, the second one is set in the job field. It'd be more logical and consistent to set up timezone only once. My suggestion is:@at <datetime>
should use RFC3339 without timezone like in civil.DateTime.@at <datetime>
should take into account the value of the job timezone field, like any other expressions.The text was updated successfully, but these errors were encountered: