Deployments have completely stopped- Webhook not delivering after reconnect

ThroopTroop · 2026-07-21 23:40:21.406294

My Vercel project has stopped creating deployments entirely since June 15, 2026 (last successful deployment: commit `6161a59`). Since then, 140+ commits have been pushed to `main` on the connected GitHub repo, but none have triggered a deployment — no build failure, no blocked deployment, nothing in the project's activity log at all. What I've already tried: * Ruled out a git-identity/permissions issue (two blocked commits from June 23-24 were unrelated and fixed same day) * Disconnected and reconnected the Git integration — this created a new git credential, but zero deployments have triggered since, even with fresh commits pushed afterward * Manually triggered "Create Deployment" for the `main` branch — also produced no result and no error I used the Vercel Agent chat to investigate, and it identified 10+ blocked deployments still stuck in the queue from June 23-24 (tied to an unrecognized git identity), plus confirmed no webhook events have been recorded since the reconnect. It suggested this needs internal log access to diagnose the webhook delivery chain, but CI/CD support cases are gated behind a paid plan on my Hobby account. Has anyone else hit a stuck/dead webhook after reconnecting the Git integration? Any workarounds (e.g., re-importing the project fresh) that resolved it for you?

Hi ThroopTroop,

Since pushes do nothing and “Create Deployment” for main also produced no deployment or error, I’d separate this from a normal build failure. A failed build should still create a deployment record; your issue sounds like the deployment is not being created at all.

A few low-risk checks/workarounds I’d try:

git log -1 --oneline
git branch --show-current
vercel whoami
vercel project inspect
vercel list

Make sure the CLI is scoped to the same team/project you’re checking in the dashboard.

Then test one non-Git path from your local checkout:

vercel deploy --target=preview --debug

If the CLI creates a deployment, the project can still deploy and the problem is likely limited to the GitHub/Vercel Git event path. If the CLI also fails before creating any deployment record, that points to a broader project/team deployment creation issue.

For a workaround, I’d import the same GitHub repo into a brand-new temporary Vercel project without moving domains or production env vars yet. Push one tiny test commit to main.

If the new project deploys, the old project’s Git linkage/queue is probably stuck, and migrating settings may be the fastest recovery path. If the new project also does not deploy, I’d look at the GitHub App installation/repo/account layer instead.

One more thing: if you create a Deploy Hook as a test, don’t post the hook URL publicly. If it ever gets shared, delete it and create a new one.