Good Morning Alteryx Community,
Yesterday my team went through the process of upgrading Alteryx Server from 2022.3 to 2023.2.
We have a lot of our workflows scheduled, and what we noticed was that post-upgrade our workflows were running one hour earlier than they are scheduled. There is a discrepancy between what the Gallery UI shows as the scheduled time (when the workflow should run) and when the workflow actually runs.
We suspect it has something to do with DST, but there was no issue with our schedules earlier this week after clocks moved an hour back over the past weekend up until the Server Upgrade.
Has anyone in the community ran into this or a similar issue when upgrading Server?
Thanks!
Hi @bfitz133 ,
I haven`t upgraded any client server to 23.2 but I have never experienced this before with other versions. Since it is the most recent version and also release 1, this could be a new unidentified issue.
Couldn`t find anything about it on the release notes. https://help.alteryx.com/current/en/release-notes/server-release-notes/server-2023-2-release-notes.h...
I would recommend opening a ticket with Alteryx support through the Case Portal and let them take a look.
Best,
Fernando Vizcaino
We are seeing the same issue. I've opened a support ticket.
Hi Garretes,
have you heard back on this?
Hi Shady;
Here is the reply on from Alteryx on the ticket. This is a workaround which requires reschedule on (all) workflows.
We are currently working on this issue and we would like you to try the below workaround and let us know if this works: Turn off Windows Date & Time setting to 'Adjust for daylight saving time automatically'. Set the Windows time zone to match the user profile time zone to eliminate additional time zone conversion. Create a schedule matching user profile time zone. Turn on 'Adjust for daylight saving time automatically' in Windows Date & Time settings and restart AlteryxService. Please recreate schedules as long as AlteryxService has been restarted after Windows 'Adjust for daylight saving time automatically' setting has been updated.
For now, we rescheduled all of the workflows manually to an hour ahead of when we want them to run.
Scott Garrett
We noticed this issue as well. Runs were scheduled 30-45 minutes after routine FTP transfers and began to fail after the switch from CDT to CST (flows would fire before data became available).
@patrick_digan, Check any familiar jobs and see if they run 1 hour earlier. Our server was on 23.2.1.7
Hi,
The issue is a known defect in 2023.2.
TGAL-9200 Schedules running an hour earlier than the scheduled time
There is no current workaround other than scheduling an hour later than expected.
The fix for this daylight saving issue will be introduced in 2024.1.
For now, please reset the schedules that are impacted to be 1 hour later.
Hello everybody,
For information, I have also opened a case today for this issue to know if a solution have been found and the answer is :
The issue is a known defect in 2023.2.
TGAL-9200 Schedules running an hour earlier than scheduled time
There is no current workaround other than scheduling an hour later than expected.
The fix for this daylight saving issue will be introduced in 2024.1.
For now, please reset the schedules that are impacted to be 1 hour later.