v0 (Vercel) · 145d ago
Increase in Workflow runs stuck as pending
ResolvedYes — v0 had a problem on June 25, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved.”
Timeline
Started: 6/25/2026, 7:45:00 AM
Last update: 6/25/2026, 1:43:22 PM
Resolved: 6/25/2026, 1:43:22 PM
Affected: c3yjhlfbv34z
Updates
resolved
This incident has been resolved.
6/25/2026, 1:43:22 PM
monitoring
The fix has been fully rolled out and we are monitoring the results.
6/25/2026, 1:30:43 PM
identified
We are currently rolling a fix for the issue. We are monitoring the results.
6/25/2026, 12:15:05 PM
identified
We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs.
6/25/2026, 10:42:09 AM
identified
The issue has been identified. We are continuing to work on a fix for this issue.
6/25/2026, 9:25:34 AM
identified
The issue has been identified and a fix is being implemented.
6/25/2026, 8:27:40 AM
investigating
We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.
6/25/2026, 7:45:00 AM
More v0 (Vercel) incidents
- Elevated Sandbox and Blob request latency and errors — resolved, 7d ago
- Build delays and degraded Vercel Dashboard performance — resolved, 12d ago
- Delays in Logs and Observability data — resolved, 25d ago
- Increased build and deployment failures — resolved, 36d ago
- Delays in Drains, Observability, and Workflow in Washington (iad1) — resolved, 38d ago
- Vercel Auth login failures for pages with Deployment Protection enabled — resolved, 42d ago