We’re looking into why this is happening. The cancel button on a run doesn’t actually stop it right now. The current workaround is to suspend and then unsuspend the cron to force-cancel the run. If that doesn’t do the trick, please reach out to our support team.
Posted Nov 13, 2025 - 15:40 UTC
This incident affected: Oregon (Cron Jobs), Frankfurt (Cron Jobs), Ohio (Cron Jobs), Singapore (Cron Jobs), and Virginia (Cron Jobs).