Scheduled automation ran twice

[cordoor-work]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Regarding automation, I had new agents created last night that I scheduled to run this morning at specific times and they all ran twice. As an example, one was scheduled for 7 AM (GMT+1) but ran at 6 AM (GMT+1) and at 7 AM (GMT+1). Another one scheduled at 8 AM (GMT+1) already ran once at 7 AM (GMT+1) and is now running again at 8 AM (GMT+1).

Steps to Reproduce

I created the automation with a scheduled to run at 7 AM (GMT+1).

Expected Behavior

I expected it to run at 7 AM (GMT+1), not 6 AM (GMT+1) and 7 AM (GMT+1)

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Automations

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. I can see the screenshots with the run history. You’re right, each automation runs twice: once an hour earlier (in UTC) and then again at the correct local time.

This is a known issue with timezone handling in the cron schedule for automations. The team is aware, but we don’t have an ETA for a fix yet.

While we don’t have a fix, try deleting the current automations and creating them again. That might help since the issue could be related to when they were created (it may have lined up with a deployment). If recreating doesn’t help, please share the Automation ID so we can check the backend.

Let me know how it goes.