Vercel is not building any of my commit, not even triggering the build

Help
1

While developing my web service, Vercel suddenly stopped triggering builds. It doesn’t even attempt to build—there are no failed builds, just no build attempts at all. After hours of troubleshooting, I gave up and migrated the Vercel project to a new one. The initial build after migration was successful, but subsequent commits from GitHub still fail to trigger new builds. Vercel isn’t detecting new pushes, so no build attempts are made, and no logs are generated in Vercel.

Migrating to a new project didn’t resolve the issue. While the initial build succeeded, the same problem persists: new commits are not triggering builds, which was the reason for the migration in the first place.

Here are my findings to narrow down the issue:

  • Git and Vercel are properly connected, as the initial build completed successfully and deployed without issues.
  • After the initial build, new pushes to GitHub do not trigger builds on Vercel.
  • GitHub confirms the new pushes, but Vercel doesn’t detect them, resulting in no build attempts or logs.
  • Since no build attempts occur, environment variables and Vercel billing overages are not the cause.
  • The branches used are main and dev, both configured to trigger automatic builds in Vercel, so this isn’t the issue.
  • Automatic deployment is correctly configured in Vercel.
  • The Vercel GitHub App is set up in GitHub’s connected apps and has access to all repositories.
  • I use a single GitHub and Vercel account, so there’s no issue with using the wrong account.
  • My project includes vercel.json, next.config.js, and package.json. If these files had issues, the initial build after migration would have failed, so they are not the cause.

Below are the captures of my settings in Github and Vercel, the integration is fine but the commits after the initial migration didn’t trigger the build.

Pasted_Image_7_31_25__10_06 AM
Pasted_Image_7_31_25__10_06 AM2746×1504 243 KB

Pasted_Image_7_31_25__10_08 AM
Pasted_Image_7_31_25__10_08 AM1914×1058 116 KB

Pasted_Image_7_31_25__10_09 AM
Pasted_Image_7_31_25__10_09 AM2698×1122 245 KB

Pasted_Image_7_31_25__10_10 AM
Pasted_Image_7_31_25__10_10 AM2790×806 126 KB

Can anyone provide insight into why Vercel isn’t recognizing new pushes from GitHub? Thank you in advance.

4

Sometimes a configuration error can prevent a build from starting at all. In that case, you may see it reported on GitHub. Looks like there are some errors on the more recent commits in your screenshot. Those red Xs may have the answer.

I use the CLI to figure out what’s wrong whenever I see this kind of thing. You can use vercel build on the local repo and it’ll either succeed (which means there’s a difference between the local and deployment environments) or it’ll fail and give you the reason.

Please give that a try and let me know if you have any other questions