- Create a workflow with multiple triggers created in the local timezone.
- Navigate away from the triggers, then re-open the trigger panel.
- Observe the first trigger appears as UTC (unexpected)
- Select a different trigger. It appears as Local
- Select the first trigger again. It appears as Local, as expected.
Hi @kevinsplx, thank you for surfacing this issue and providing detailed steps to reproduce it. I can confirm it's a bug. It appears to be limited to the UI, the trigger still runs at the correct time on my end.
We created a bug report and will update you here when it's fixed. Please let us know if your WF is running at a different time than the one you selected.
They run at the correct time as far as I can tell; just a weird UI glitch.