Changes / Inngest / Degraded Function Execution
Inngest: Major incident: Degraded Function Execution
Summary
Inngest reported a major function-execution degradation causing failed runs or delayed scheduling from incoming events, starting 2026-09-04 18:26 UTC and resolved at 2026-09-04 19:10 UTC (43 min). The vendor said it identified the cause without disclosing details; customers can replay failed runs in the UI.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: outage (model (Jev), 68%)Changed Detected Source: status.inngest.com (opens in new tab)
What changed
Before: not present
After: Degraded Function Execution
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-04 18:26 UTC
Before: not present
After: 2026-09-04 19:10 UTC
Before: not present
After: We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
Before: not present
After: We are actively investigating an issue with execution. Users may experience failed runs or delayed scheduling of runs from incoming events.
We will provider further updates as we identify the cause and resolve the issue.
Before: not present
After: We have identified the cause of the issue and we're monitoring the system as it is currently recovering. If users experienced any failed runs, you are able to replay failed runs in the UI. More info can be found here: https://www.inngest.com/docs/platform/replay#how-to-create-a-new-replay
Before: not present
After: The incident is now resolved and the system is full operational.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Degraded Function Execution (this change) Inngest reported a major function-execution degradation causing failed runs or delayed scheduling from incoming events, starting 2026-09-04 18:26 UTC and resolved at 2026-09-04 19:10 UTC (43 min). The vendor said it identified the cause without disclosing details; customers can replay failed runs in the UI. | Major incident |