Changelog
Every update to Primentra, 15 releases so far. Search it to find when something changed.
Fixed
4- The next run is the time you configured. Set 18:00 and the status bar says 18:00, on every server, whatever its time zone. The run times you type are unchanged — they were always local wall-clock times, and now the scheduler treats them that way
- Scheduled batches fire on time. The dispatcher compared the next run against UTC, so on a server ahead of UTC every schedule ran late by the offset, and on one behind UTC it ran early
- The Last run time, the trigger debounce window and the stuck-batch timeout are measured on the same clock, so a schedule and its history no longer disagree by the offset
- The Scheduler Log shows the time an event actually happened. Existing scheduler times are corrected once during the upgrade — nothing needs to be reconfigured