Vercel Deployment Failures

I’ve made a couple of commits to my repository, and while GitHub workflows are passing successfully, Vercel deployments are consistently failing across multiple environments: jailbreak-changelogs-old, jailbreak_changelogs_prod, and jailbreak_changelogs_test. The error message simply states "Deployment failed" with a "Details" link, but clicking on it does not provide any additional information or logs to diagnose the issue.

This is preventing my website from being updated to reflect the latest commits. Has anyone encountered a similar issue with Vercel deployments failing silently? Any suggestions on how to troubleshoot or resolve this would be greatly appreciated.

Additional context:

GitHub workflows are passing without errors.

The issue seems isolated to Vercel deployments.

No detailed logs or error messages are accessible via the "Details" link.

Going to Deployments Tab on Vercel dashboard doesn't show the failed deployments.

Repo can be found here: https://github.com/JBChangelogs/JailbreakChangelogs

GitHub

GitHub - JBChangelogs/JailbreakChangelogs: Your comprehensive platform for Jailbreak item values, trade listings, update tracking, and community features. Get accurate trading data, post trade ads, track seasonal changes, and connect with other players!

Your comprehensive platform for Jailbreak item values, trade listings, update tracking, and community features. Get accurate trading data, post trade ads, track seasonal changes, and connect with o...

So I tried running the Vercel CLI tool, first I ran vercel build it worked well, no errors Then I ran vercel deploy and it returned the following

Vercel CLI 41.1.4
Error: Resource is limited - try again in 3 hours (more than 100, code: "api-deployments-free-per-day").```

I just checked https://vercel.com/docs/limits/overview and I did not create 100 commits today, so it doesn't make sense why I am being limited. If you check commits for today, I have not made 100 commits so it can't have deployed 100 times today.

Hey . It looks like you've exceeded the limit for deployments created per day. It's currently 100 in a 24 hour period for the Hobby plan. Looking through the activity logs, it does appear that there were a large number of deployments created within this time period.

I recommend checking on any automated processes you may have configured which could have caused an increase in deployments. For example, a CMS configured to deploy each time a small change is saved could cause excess deployments.

I hope that helps!

Oh thank you for that, had no idea I had exceeded 100 commits. Must be some workflow I made today that caused the issue.