Vercel deploy hook creates job but deployment never appears or executes

Project: clientdining-v1 (prj_iCWwDrvZcgZqk41hcnCOTH4o6CAT)

Issue: When I trigger my Deploy Hook, I get a successful 201 response with a job ID in PENDING state, but:

  1. No deployment appears in the Deployments UI
  2. The site doesn’t update with new code
  3. This happens both via GitHub webhook and manual URL trigger

Deploy Hook URL: https://api.vercel.com/v1/integrations/deploy/prj_iCWwDrvZcgZqk41hcnCOTH4o6CAT/em9GRyROK5

Example response:

{“job”:{“id”:“mA0ORkK8IgBb3b6j3wFH”,“state”:“PENDING”,“createdAt”:1769166753635}}

The only way I can deploy is by manually clicking “Redeploy” in the UI, but this doesn’t pull latest commits from GitHub.

Any help appreciated!

To assist you better, could you please provide the deployment/build logs as well as your configuration files (next.config.js and vercel.json)? This information will help us pinpoint the issue more effectively. Happy to help!

Facing the same issue. Receive a response from api akin to above:

{“job”:{“id”:“mA0ORkK8IgBb3b6j3wFH”,“state”:“PENDING”,“createdAt”:1769166753635}}

But deploy never actually gets created/triggered

I’m seeing the same issue on my project.

Project:
v0-scan-lynk-healthcare-website

Repository:
MahirAltib/scanlynk

Issue:

  • GitHub pushes to main are not creating deployments

  • Deploy hooks return pending job IDs, but no deployment appears in the Deployments list

  • Production remains stuck on an older commit

Deploy hook responses:

  • {“job”:{“id”:“ZVe8VeTxIv00cSQkGseX”,“state”:“PENDING”,“createdAt”:1778724399406}}

  • {“job”:{“id”:“vYzSwc87LGea8AesiYos”,“state”:“PENDING”,“createdAt”:1778725187745}}

Current state:

  • latest live production is stuck on commit 573cc39

  • latest GitHub main is at commit 60a2dcb

What I already tried:

  • verified the GitHub repo connection in Vercel

  • disconnected and reconnected the repository

  • created and triggered a new deploy hook manually

  • confirmed the latest commits exist on GitHub main

Like the original post, the only visible production deployment remains the older one, and new pushes/hooks do not create new deployments.