GitHub Push Events Not Triggering Vercel Deployments

Help
1

I’m experiencing an unusual issue with my Vercel deployments where they get triggered correctly but remain in “PENDING” state indefinitely.

Specific Problem:

  • Deployments are successfully triggered (I get a job ID)
  • Status shows as “PENDING” but never progresses to building or deployment
  • This occurs with both GitHub webhook triggers and direct deploy hook calls
  • I’ve tested the deploy hook directly with curl and while it returns a job ID with PENDING state, it never progresses beyond that
  • Response shows: {"job":{"id":"...","state":"PENDING","createdAt":...}} but it never advances

What I’ve already verified:

  1. Git integration is correctly set up in Vercel
  2. GitHub repository has proper permissions
  3. Commit author email/username matches my Vercel account
  4. “Ignored Build Step” is set to “Automatic”
  5. GitHub webhooks are correctly delivering events (status code 201)
  6. There are no visible error messages in the Vercel dashboard

Environment:

  • Next.js application
  • Private GitHub repository
  • Hobby tier Vercel account

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?

2

Can you share an example job ID?

3

Sure can:

{
“job”: {
“id”: “3F2Zqas4ehlGBVSVcrZi”,
“state”: “PENDING”,
“createdAt”: 1743788656714
}
}

4

Thanks! We are working on improving this error message, however the actual error is:

api call failed with "Redirect at index 0 has invalid `source` pattern "https://www.naturalsupplementsearch.com/:path*".

1 Like
5

Wow, thank you so much. The actual error message helped me fix it.

2 Likes
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.