I am setting a schedule in retool workflow
(CRON that runs on EST timezone at 00:40,01:40...,07:40 every day.
After saving it - it actually runs as expected but the schedule itself returns to UTC at 12am every day, which is the default.
Did anyone run into this issue ?
Hello @taluk,
Very odd issue. Once you save the workflow trigger it should not be switching back to the default.
So you are saying it runs at the expected time that you wanted, but visually, the workflow displays the trigger block saying "UTC at 12am" but it does not run at that time, correct?
There is a known issue of apps resetting to previous states when there are either multiple tabs open looking at the same app or when multiple users are trying to edit the same app before/without the 'multiplayer' feature enabled.
If you have another tab on another computer or browser that is open and viewing the default app, it might be sending 'save' events periodically to the app, without the changes you made, causing the app to think that you are wanting to save it with the default setup.
Have you noticed any patterns for when the change occurs that shows UTC 12 am?
I think this might be the same issue I am experiencing: I also have workflows where I have set the schedule in EDT, and in the logs, it looks like they are running at the correct time. However, based on the output in my application, I don't think they are.
Here is the recent run history for one of my workflows. As you can see, after 2024-10-18, I changed the schedule from 9pm 4 days a week to midnight every day. The change to every day is definitely working as expected. However, when I look in my application database (outside of Retool), I see that the creation time of the output data is the same for records created after the change as before: a few minutes after 21:00, local time.
I thought I'd made a mistake setting the schedule, so I opened the Triggers and opened the Schedule panel, and I see 12:00 AM UTC. However, I also noticed that the Save Changes button is enabled, which I found odd because I hadn't changed anything.
The top of the page is also showing, as expected, that the latest version is deployed.
If I change the schedule back to what I thought I set it to, the button disables.
Any help on this is much appreciated, as I do have several workflows that control time-sensitive processes for the business.
Here is an example from another workflow that I just created today, and have only set the schedule once: I set it to 11:00 PM EDT, but you can see that the Schedule panel shows 12:00 AM UTC, which is different from what is shown in the Triggers panel and the startTrigger block.
An edit, with apologies: I have found another explanation for why some of the output data appeared to have been created at the wrong time: it was an unfortunate coincidence and not related to the scheduler issue. I now believe this is a UI bug only.
Hi Jack and Emily,
Sorry for the delayed response here.
My workflows runs on time as I originally scheduled them (e.g. schedule time and timezone) - so this works as expected.
The thing is that the UI is quite confusing when opening the schedule box you can't see the original setting , and in the startTrigger you can't tell the exact timezone selected:
another weird UI issue IMHO is that when clicking "Edit triggers" I can see in the left side a part display of my saved schedule but on the right side it elapses to default.
Jack, per your question I don't have multiple tabs opened and i'm the only one working on these workflows.
It happens on all of my workflows and I find it hard to follow the schedules this way.
Happy to give more details if needed.
That is great to hear you were able to you were able to get figure out the time issue!
I was scratching my head as you had a great presentation and explanation but I was not sure what could be causing the discrepancy 
If it a UI bug that should be much easier for us to remedy 
Thank you for the reply and additional details!
It seems that the consensus is this bug is limited to the UI, where it incorrectly displays the default time.
I can send a bug report for this to our engineering team and hopefully get this sorted quickly. As your second screenshot clearly shows the discrepancy between the left side displaying the correct trigger times and the right side UI glitching out to default 
I can also make a feature request to display the time zone in the trigger block's UI, as I agree this would be very helpful.
For the second part of your comment, "when opening the schedule box you can't see the original setting", could you elaborate more on this? By original setting are you referring to what the trigger blocks display when you first create them(12AM)?
Hello @taluk!
I got word from our engineering team that this doesn't seem to be an issue anymore. Let me know if you are still experiencing the trigger schedule disappearing 
