Cloudflare Workers - Cron Trigger Activation Issues
Cloudflare · Last saved provider status: monitoring
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- monitoring
- Provider impact
- minor
- Provider record created
- 12 Oct 2026, 19:09:20 UTC
- Provider record updated
- 12 Oct 2026, 19:39:43 UTC
- Explicit provider start
- 12 Oct 2026, 19:09:20 UTC
- Explicit provider end
- Not available
Affected components reported by the provider
- Workers
57srcl8zcn7c
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Cloudflare's complete published platform report and provider locations. These are provider reports, not independent network observations or evidence of an application's upstream dependencies. Workers AI, AI Gateway and Replicate have separate component views.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- monitoring
A fix has been implemented and we are monitoring the results.
Seen in a saved revision at 12 Oct 2026, 19:49:48 UTC - investigating
Cloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
Seen in a saved revision at 12 Oct 2026, 19:49:48 UTC