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.

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

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

https://www.githubstatus.com/incidents/gxycch3076xk

Are you still having trouble with this?

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:

1
vercel whoami
2
vercel link
3
vercel deploy --prod --debug
4

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:

1
{
2
  "github": {
3
    "enabled": false
4
  }
5
}
6

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:

1
*/15 * * * *
2
0 */6 * * *
3

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.