Vercel incident

Increase in Workflow runs stuck in pending, failed

Minor Resolved Upstream link ↗

Started

July 1, 2026 at 04:57 PM UTC

Duration

1h 33m

Resolved

July 1, 2026 at 06:30 PM UTC

Updates timeline

  1. 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.

  2. 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.

  3. 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.

Live Vercel status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader