Increase in Workflow runs stuck in pending, failed

What to do

• Check whether you use Vercel Workflow. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 33m it lasted.

  Anything that failed between 2026-07-01 16:57 UTC and 2026-07-01 18:30 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 3

1. identifiedJul 1, 2026, 4:57 PM UTC

   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.

   provider

2. identifiedJul 1, 2026, 5:49 PM UTC

   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.

   provider

3. resolvedJul 1, 2026, 6:30 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.