Cron automation stopped running

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

We have a Cursor Cloud Automation that has been successfully running on a daily schedule. Yesterday and today it didn’t run. Seems it stoped running. Other event-triggered and scheduled Automations run by this user are running fine. When I run the automation manually, it runs fine. I tried removing the cron schedule and adding it back - still didn’t run on schedule.
https://cursor.com/automations/583f2b92-7476-11f1-a8a0-cafc5ef88358/

Steps to Reproduce

Not relevant. Cron.

Expected Behavior

The Automation should run on schedule.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Not relevant

For AI issues: which model did you use?

Not relevant

For AI issues: add Request ID with privacy disabled

Not relevant

Additional Information

In the “Where does the bug appear (feature/product)?” dropdown, you should add an option for “Cloud Automations”

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Shahar_Barak ,

You’re not doing anything wrong. We’ve confirmed this is on our side: the automation stopped firing on schedule even though it’s still active, no failed run was recorded, and manual runs work. That matches a pattern we’ve seen where a single scheduled automation silently stops triggering. It’s isolated to this one automation, which lines up with your other automations running fine.

Two things:

  1. You re-added the schedule this morning, but that was after today’s run window had already passed, so it hasn’t had a chance to fire yet. Watch tomorrow’s scheduled run first - if it fires, you’re set.
  2. If tomorrow still skips, the most reliable workaround we’ve seen is to recreate the automation fresh rather than editing the existing schedule in place: leave the current one disabled to keep its history, then create a new automation with the same prompt, tools, and schedule. A new automation comes up with a clean schedule and clears this state.

We’re looking into the underlying cause. If tomorrow’s run is still missing, reply here and I’ll take it from there. Also - good callout on adding “Cloud Automations” to the bug-form dropdown.

I changed the schedule earlier today to run today at a future time and it didn’t run (I then changed it back to the original schedule).
To recreate a fresh automation, do I need to recreate a new one from scratch or using the duplicate feature would be enough?