Netlify Scheduled Functions Fail to Auto-Trigger April 13 Outage
What happened
Netlify experienced a service disruption on April 13 where scheduled functions failed to auto-trigger as programmed. The incident was resolved at 01:16 UTC after Netlify deployed a fix for the underlying issue affecting scheduled invocations. During the outage, manual function executions continued to work normally, but automated scheduled runs did not trigger according to their configured schedules. The incident affected enterprise teams relying on scheduled functions for automated workflows, data processing, and maintenance tasks.
Business impact
Background
Scheduled functions are essential infrastructure for enterprise teams managing automated workflows, particularly for tasks like content publishing, data processing, and system maintenance. Netlify's serverless platform is widely used by development teams for deployment and automation. Function scheduling reliability is critical for operations that must execute at specific intervals to maintain data integrity or meet compliance requirements.
What this means for your team
What to watch
Monitor Netlify's promised root cause analysis for this incident to understand whether additional safeguards are needed. Teams should verify that any missed scheduled functions during the outage period are manually executed if business-critical.
Sources
-
Incident with Pages
GitHub Status
-
Wrangler logins failing due to scope error
Cloudflare Status
-
Scheduled Functions Auto-Triggering Not Executing
Netlify Status