[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Vercel deploy hook stuck in PENDING state for Next.js monorepo

41 views · 0 likes · 2 posts


Hiregram (@hiregram) · 2026-03-02

Similar ticket raised under Vercel community (for reference): [https://community.vercel.com/t/github-push-events-not-triggering-vercel-deployments/8082](https://community.vercel.com/t/github-push-events-not-triggering-vercel-deployments/8082)

Hi, facing the same issue described here - deploy hook returns `PENDING` but deployment never progresses.

## Setup

- Next.js 15 app inside a monorepo (`frontend` subdirectory)
- Vercel project root directory set to `frontend`
- GitHub Actions workflow `POST`s to a Vercel Deploy Hook on every push to `develop` branch
- Git Integration also connected to `hiregram-ai/hiregram`

## Symptom

Deploy hook call succeeds and returns a job ID, but the deployment never moves past `PENDING` - no build starts, nothing new appears in the dashboard or `vercel ls` output.

```json
{
  "job": {
    "id": "...",
    "state": "PENDING",
    "createdAt": "..."
  }
}
```

## What we’ve already ruled out

1. Recreated the deploy hook (old URL was silently returning `404` for months)
2. Changed **Ignored Build Step** from `Automatic` to `git diff HEAD^ HEAD --quiet` (Reverted to `Automatic` now)
3. GitHub webhooks are delivering correctly with status `201`
4. `vercel deploy --yes` from CLI builds and deploys successfully
5. `next.config.ts` has no redirects or rewrites - it’s essentially empty
6. Git Integration is connected and shows as active in **Settings → Git**

Pushed two test commits to `develop`, waited 5+ minutes each time - zero new deployments appeared.

I’m specifically looking for help understanding why deployments get stuck in `PENDING` and never progress, despite being triggered successfully. Has anyone encountered this issue before, or are there any Vercel system limits or configurations that might cause this behavior?


system (@system) · 2026-03-02

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

[https://community.vercel.com/t/debugging-404-errors/437](https://community.vercel.com/t/debugging-404-errors/437)

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking [v0](https://v0.dev/).