Evaluation uses UTC time instead of scheduled (local) time
W
Wouter van Dijk
Please make it possible to run the evaluations at local time.
We noticed that evaluations where not complete when running the scheduled task at 12:00 or 1:00. It turns out the evaluation is done on UTC time instead of the local time (currently UTC+2). For example, this causes the evaluation to take place at 11:00 the previous day wen scheduling the import at 1:00.
This is very confusing and inconsistent. This also makes it not possible to run the evaluations as soon as possible. We want the actions to be enforced as soon as possible on a new day. Especially the disable and update actions. Now the earliest time we are able to enforce the actions is between 2:00 and 2:59 (depending on when the schedule is executed). Also we have target systems that have their own import we have to schedule after this.
W
Wouter van Dijk
After implementing https://helloid.canny.io/provisioning/p/different-time-schedule-options-for-scheduling and specifying a specific time zone, you would expect even more so that the evaluation would take place in the specific time-zone you configure in the sceduling.
There is no mention that the evaluation takes place in UTC time anywhere.
Worst case scenario is that a customer only has one sceduled import, is not aware about the fact that the evaluation takes place in UTC time (because how could he) and the enforcement actions are consequently a day behind or ahead because of the timezone difference (between UTC-12 and UTC+12).
Also when you are aware of the issue, the forced shifting of the sceduled time can cause unwanted side effects. Security or otherwise.
We are lucky that in our case the difference is only +2 (summertime) or +1 (wintertime).