I have a cursor automation that is supposed to run every hour. It was running without issue until on March 20th (last successful run). My other automations (daily) run without issues, and manual trigger works without issue.
Thank you for the detailed report with the automation ID and screenshots. I’ve investigated this on the backend and can confirm the issue.
Your hourly cron schedule IS firing correctly via our scheduling system. However, every cron-triggered run since around March 20 is being blocked because the system believes a previous agent is still actively running for this automation. Since the system prevents duplicate agents from the same scheduled automation, all new cron runs are skipped. This is why your manual triggers still work fine – they bypass this check.
The root cause appears to be a previous agent run that got stuck and never properly transitioned to a completed state, leaving behind a stale record that now blocks all subsequent scheduled runs. This coincided with a brief service disruption we experienced around that time.
Deleting the current automation and recreating it with the same configuration and hourly schedule. This should give it a fresh state with no stale records blocking new runs.
