We are noticing that the Execution timestamp and JOC cockpit timestamp are still 1 hour behind after this weekends daylight savings.
We are on 1.13.0 (2019-08-29) release and did not experience this issue in the past.
The jobs seem to be running on the right schedule (per DST change), but the timestamp seems to throw our end users off.
Any ideas why this may be happening?
Hi Raj,
we confirm this issue that was adressed in parallel by the thread DST not reflected by JOC
This issue is handled with our change management system:
Best regards
Andreas
Last edit: Andreas 2021-03-16
Thanks for the quick revert @sosap
We are also seeing this issue in NZ on version 1.13.6
See attached screenshots
Last edit: Brendon 2021-04-12
Hi Brendon, certainly JobScheduler is a non-discriminatory product: our bugs hit all our users in the same way, independent from their location.
Please consider the JIRA issue mentioned above with the indicated workaround and patch. This fix is included with release 1.13.9 that will ship later in this week.
Best regards
Andreas