Alteryx Server Upgrade 2023.2 Timezone/Gallery Issue

[bfitz133]

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!

[Chandrabalusugure]

The issue is a known defect in 23.2, "TGAL-9200 Schedules running an hour earlier than scheduled time"

The fix for this daylight saving issue is expected in 24.1.
 

Workaround:

Option -- The following workaround may help but is not correcting the issue on all Servers.

• On Server: turn off the Windows Date & Time setting to 'Adjust for daylight saving time automatically'
• Restart Server
• Reschedule the workflow

Option -- Schedule the workflow an hour later (or earlier) so it runs at the intended time.  Note that this will need to be adjusted back after this issue is resolved.

https://knowledge.alteryx.com/index/s/article/Schedules-running-an-hour-earlier-than-scheduled-time-...

[TheCoffeeDude]

I changed the default time zone on my 2023.2 server to UTC. The schedule runs as expected but the workflow results are in UTC. We can't seem to win with this.

[bfitz133]

Just as an update, our team is still utilizing the workaround of scheduling workflows an hour later than expected.

With Spring Forward approaching this Sunday, does anyone know if there will be impact to existing schedules that are currently set an hour ahead using the workaround?

[TheCoffeeDude]

We'll find out on Sunday morning what happens. If a patch is released tomorrow (Friday), I don't think I can test it fast enough to push it into my prod environment before Sunday.

[bfitz133]

Looks like for us that Spring Forward did have impact- everything ran at scheduled time. So our schedules that were set one hour ahead with the workaround, actually started running at that time on Sunday.

Our team will now be moving everything back an hour as a result.