Hi!
Since after September 2nd, I’ve noticed that the deploy hook for my project is no longer triggering builds. I typically have a GitHub action hit the hook url, but manually hitting it with curl is also no longer working. All of the responses from the hook url are giving valid JSON with status: PENDING
Can someone from Vercel please check the job logs to help me figure out what’s wrong? Some recent job IDs:
nKHro8S5oLIa8xLJAY9l
dtvEqTQKcECBy1OgLXr1
hi3zd4M0yLVSwTf3hjEd
thanks ~
Btw, I’ve looked at the solution to this post: https://community.vercel.com/t/deploy-hooks-doesnt-trigger-any-deployment-they-used-to-work-fine/17710
My repo is private but it is under a personal Github account (not an org).
I checked the logs and see "deployment is blocked due to insufficient permissions. The github user DELETED ACCOUNT is not part of the team." Can you check your git metadata matches your GitHub account?
https://community.vercel.com/t/auto-deploy-from-github-not-working/3137/7?u=amyegan
Hi ! Thanks for taking a look.
Can you verify that the person who made the commit is a current member of your Vercel team?
Yep, here’s a screenshot of the email settings for the account making commits:
and the email in Vercel:
It’s odd that DELETED ACCOUNT is showing up in your logs…I haven’t deleted any github accounts associated with the repo that’s connected to Vercel.
What I was asking about is specifically for your local commit settings. Can you double check that git config --global user.email returns the same email?
Anyone found a solution to this. It’s already a really great problem now.
Starting getting an issue like this today on my production branch. Deployments are starting from my preview but when I merge to or commit to my production branch no deployment starts. Big problem!!!
Also I am unable to manually start a deployment for the production branch. I get “An unexpected internal error occurred”.
{"error": {"code": "internal_server_error","message": "An unexpected internal error occurred"}}personal GitHub, private repo.
I believe the error you saw was related to this incident: Build and Deployment Errors When Creating New Deployments
It's been resolved and you should be able to deploy now. Do you still see this error on new deployments?