New deployments not being created for project (git push & deploy hooks broken)

Help
1

Hi, I am unable to make any deployments to Vercel from my Git. It stopped working 3 days ago. Have tried to run fixes recommended by support chat and AI but still not deploying: Here are the details:

Project ID: prj_gy1hOdAeWnDmvSzvNpl6SrEIyo4M

Issue Summary: New deployments are not being created through any trigger, but redeploying existing deployments still works.

Timeline:

  • Issue started around 2026-07-11
  • Last successful auto-triggered deployment was commit d369556 on the dev branch

Symptoms:

  • Git pushes to dev branch no longer trigger deployments (this was working before)
  • A brand-new branch (deploy-test) pushed also produced no deployment
  • Deploy hook returns a valid API response with a PENDING job ID, but no deployment ever appears in the dashboard
  • Manually clicking “Redeploy” on an existing deployment does work

Troubleshooting already attempted:

  • Disconnected and reconnected the GitHub repo in Project Settings → Git
  • Verified Vercel GitHub App is installed and has repository access
  • Tested with a fresh branch
  • Triggered deploy hook multiple times — returns PENDING but nothing happens

Environment:

  • Branch: dev (configured as active in Vercel)
  • Hobby plan

Expected behavior: Git pushes and deploy hooks should create new deployments as they did before 2026-07-11.

Actual behavior: No deployment is created. Deploy hooks return PENDING status but no deployment materializes in the dashboard.

2

Update — Additional testing:

Created a brand new Deploy Hook for the dev branch and triggered it with curl.

  • Response: {"job":{"id":"EVxS8O9U8dUnb7X6XjHJ","state":"PENDING","createdAt":1783943377869}}
  • Result: No deployment appeared in the dashboard

This confirms the trigger is being received but not making it into deployment creation.

3

I have a similar issue, did you find a solution?

4

There was a recent GItHub incident which would have affected deployments that’s been resolved

Are you still having trouble with this?

5

Hi BNA5950,

For this specific “deploy hook returns 201 / PENDING, but no deployment record appears” pattern, I’d try to surface the hidden validation error with the CLI from a clean local checkout:

vercel whoami
vercel link
vercel deploy --prod --debug

The reason I’d do that is because some project config validation failures can block deployment creation before anything useful shows up in the dashboard.

Two config checks I’d make right away:

{
  "github": {
    "enabled": false
  }
}

If that exists in vercel.json, deploy hooks will not trigger deployments.

Also check for crons in vercel.json. Since this is a Hobby project, a schedule that runs more than once per day, like:

*/15 * * * *
0 */6 * * *

can fail deployment validation. If you have a frequent cron, try removing it temporarily or moving it to an external scheduler, then push one tiny commit to dev.

If vercel deploy --prod --debug shows a clear config error, that’s probably the blocker. If the CLI deploy succeeds but Git pushes and deploy hooks still never create a deployment, then I’d include the hook job ID, branch name, UTC timestamp, and confirmation that the CLI path works.