Hello community, when I set a schedule on a workflow, update the workflow and go back in to edit it and then update it again I get the error message below, has anyone else seen this behavior?
After some investigation we were able to reproduce this in engineering by updating the workflow task settings from a browser that was in a UTC+00:00 or above time zone.
The issue itself happens for scheduled times, particularly on Monday, where each task update will subtract 2 hours from the time set until the day value turns to -1 which causes the error seen in the screenshot.
As a workaround, you can clear the schedule and manually set it every time you need to update the workflow task settings.
Hopefully you won't be doing too many updates that require you to clear the schedule often.
Can you ensure that all instances and the browser are all on the same time zone? We want to ensure there are no discrepancies between the instance time zone and the browser time zone.
Meanwhile, engineering will incorporate the permanent fix as part of our next release.
We have not seen this, but it seems to indicate that the day field (0-6, with 0 being Monday) is being sent to the REST API with an invalid value, or is being interpreted incorrectly as the wrong value. We'll look into this and get back to you.
That also explains why the schedule jumps back two hours after saving it!
Retrieving data ...