BREAKING: Vercel MAJOR 🚨 Workflow runs stuck as pending [x4ngbgzymq4h]

Vercel experiencing significant disruption with workflow runs stuck in pending state. Immediate workarounds for indie hackers inside.

BREAKING: Vercel Workflow Runs Stuck as Pending 🚨

Status: Identified | Severity: MAJOR | Updated: Now

---

What's Down & Who's Affected

Vercel's GitHub Actions integration and workflow execution pipeline is experiencing a major bottleneck. Workflow runs—particularly those triggered by deployments, pull requests, and scheduled jobs—are queuing indefinitely in a "pending" state without progressing to execution.

Who this impacts:

Teams using Vercel's native GitHub integration for CI/CD

Projects with automated deployment workflows

Pull request preview deployments

Any scheduled workflow jobs

Indie hackers relying on Vercel's built-in automation

What's NOT affected:

Direct deployments via vercel deploy CLI

Existing live deployments and traffic

Static site hosting and edge functions (in most cases)

---

Immediate Workarounds (Do This Now)

1. Use Vercel CLI for Deployments

Bypass the GitHub integration entirely: ```bash npm i -g vercel vercel deploy --prod ``` This works independently of workflow infrastructure.

2. Move CI/CD to External Services

Don't wait—implement this immediately:

GitHub Actions (standalone): Create .github/workflows/deploy.yml that calls Vercel API directly

GitLab CI, CircleCI, or Jenkins: These have direct Vercel integrations

Example workflow fix:

```yaml

name: Deploy to Vercel

run: | npm run build vercel --prod --token ${{ secrets.VERCEL_TOKEN }} ```

3. Temporarily Disable Auto-Deployments

In Vercel dashboard → Project Settings → Git:

Turn off "Automatic deployments from Git"

Require manual CLI or API triggers until resolved

4. Use Vercel REST API

For programmatic deployments: ```bash curl -X POST https://api.vercel.com/v13/deployments \ -H "Authorization: Bearer $VERCEL_TOKEN" \ -d '{"name":"project-name"}' ```

---

How to Check If You're Affected

1. Vercel Dashboard: Check Project → Deployments. Do you see pending/queued items not advancing for 15+ minutes? 2. GitHub Checks: In your PR, are deployment status checks showing "Waiting" indefinitely? 3. Vercel Status Page: Visit [status.vercel.com](https://status.vercel.com) for official updates 4. Quick test: Push a test commit. Does it deploy within 2 minutes? If not, you're hitting this issue.

---

Alternative Tools to Consider (Short-term)

Netlify: Similar workflow integration, proven reliability

GitHub Pages + Actions: Free, puts you in full control

Railway, Render, or Fly.io: Independent CI/CD systems

Your own CI/CD runner: Maximum control, minimal dependency risk

*Note:* Don't migrate entirely without testing. Use these as fallbacks while Vercel recovers.

---

Monitor Recovery

Official channels:

Vercel Status Page: [status.vercel.com](https://status.vercel.com)

Twitter: [@vercel](https://twitter.com/vercel)

Vercel Community Slack (if you're in it)

What to watch for:

Workflow queue clearing

New deployments processing within 60 seconds

GitHub checks completing normally

Recovery ETA: Vercel typically resolves identified infrastructure issues within 30-180 minutes. This one is marked "identified," which is positive.

---

Bottom Line

You have working alternatives right now. Don't panic. Use the Vercel CLI for critical deployments today, implement external CI/CD as a buffer, and monitor recovery. This is a workflow infrastructure issue—your apps are still live.

We'll update as Vercel confirms resolution.