Resolved after 1 hour 33 minutes, affecting Workflow, on July 1, 2026.
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. We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state.
Affected components
Update timeline
- identified Jul 01, 2026, 04: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.
- identified Jul 01, 2026, 05: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.
- resolved Jul 01, 2026, 06: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. We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state.
Your product runs on more than Vercel
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services