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/
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:
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.
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?
I have the same problem with our automation (8d105c70-8a65-11f1-b532-320a589b8025), it’s successfully triggering on Sentry issues, but not on the daily 17:00 cron.
Hey @janri_pc thanks for adding your automation ID, that helped a lot.
What you’re seeing is a different mechanism from the one this thread was originally about, so it’s worth its own thread - could you open a new one? A couple of details that would help there: your automation ID (you’ve got it above), your timezone, and both triggers you have configured (the Sentry one and the cron).
For context on your case: because both a Sentry-triggered run and the daily cron target the same automation, when the cron time comes around it can see a Sentry-triggered run still active and treat the cron tick as a duplicate, so the cron doesn’t launch. That’s not intended behavior on our side, and this is an issue we’re tracking.
One thing worth trying while we look into it: split the two triggers into two separate automations - one Sentry-triggered, one on the cron - so the cron path can’t collide with an event-triggered run.
I’ll follow up on the new thread once there’s an update.
