Resolved -
This incident has now been resolved.
We apologise for any inconvenience this has caused.
Apr 2, 17:51 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Apr 2, 17:38 UTC
Identified -
If you are using scheduling, please be aware that changes to working patterns are not updating the schedule.
We have identified the root cause and will be publishing a hotfix to your environment tonight.
In the meantime we would suggest not making working pattern changes, however if changes are made then these will be synced during the deployment of the hotfix.
Apr 2, 11:25 UTC