Cloudflare: Delayed, missed, and duplicated Workers Cron Triggers
Affected components: Cloudflare Sites and Services - WorkersWorkers
Timeline of updates
- investigating
We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Incident silently edited: Delayed, missed, and duplicated Workers Cron Triggers
- Incident updated: Delayed, missed, and duplicated Workers Cron Triggers
- Incident updated: Delayed, missed, and duplicated Workers Cron Triggers
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2a95c0f9e557ca43…Version 2 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fd0bddb20d707ba1…Version 3 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
15ca5fedde27dfa3…Version 4 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7c5963221ce236c7…
Impact, status and times are the vendor’s own, as last archived. View on www.cloudflarestatus.com (opens in new tab).