Vercel outage, July 2026: Increase in Workflow runs stuck in pending, failed
Vercel reported and resolved an incident: Increase in Workflow runs stuck in pending, failed. It lasted 1.6 hours.
OKResolved
From Vercel's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 1.6 hours
- Impact
- minor
- Affected
- Workflow
- Investigating
- Identified
- Monitoringnot posted
- Resolved
Why it happened
Vercel has not given a cause in its updates. We never guess one.
How it was resolved
The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.
Timeline
Oldest first, from the first notice to the resolution. From Vercel's official status page, in their words.
- identified
We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.
- identified
We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted.
- resolved
The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.
What this means for a business (and what to check now)
- Retry anything that failed during the 1.6 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other Vercel incidents
- Delays in Logs and Observability data, resolved after 1 hour
- Increased build and deployment failures, resolved after 6.6 hours
- Delays in Drains, Observability, and Workflow in Washington (iad1), resolved after 1.4 hours
- Vercel Auth login failures for pages with Deployment Protection enabled, resolved after 16 minutes
- Elevated Sandbox error rates in Paris (cdg1), resolved after 25 minutes
Hear about the next Vercel incident as it starts
Free email alerts when the official status changes, with what to do while it is down.