No deployments created since Aug 12 - even manual Deploy Hook produces no build - Help

Project: crm-westborg (team: westborg-s-projects, project ID prj_TirA2MLNDTTu0mC81IbF50T7XqQi)

My project has stopped creating deployments entirely since Aug 12 (last successful commit 2975f61). Since then:

New commits pushed to the connected GitHub repo (Goverssebastiaan/crm-westborg, branch main) create no deployment.
I disconnected and reconnected the Git integration in Project Settings > Git - no change.
I created a Deploy Hook and triggered it manually via curl. It returned {"job":{"state":"PENDING"}}, but no deployment ever appeared - checked the Deployments list with ALL status filters enabled (Ready, Error, Building, Queued, Initializing, Canceled, Blocked) and nothing shows up. No entry in the Project Activity log either.
The GitHub App "Vercel" has "All repositories" access and is not suspended (verified in GitHub Settings > Installations).

This looks like builds are being silently dropped before a deployment record is even created. Has anyone seen this, or does anyone from the Vercel team have insight into what could cause this?

Found it - solved. Posting in case anyone else hits this.

Root cause: vercel.json had an hourly cron (0 ). Hobby accounts only support daily crons. The dashboard/GitHub-triggered deploy pipeline was silently dropping every deployment because of this - no error anywhere in the Deployments list (even with all status filters on) or the Activity log, and even a manually triggered Deploy Hook just returned {"job":{"state":"PENDING"}} and produced nothing.

What actually surfaced the real error was deploying via the Vercel CLI directly:


npx vercel --prod
```

That returned this explicit error immediately:

```
{
  "status": "error",
  "reason": "deploy_failed",
  "message": "Hobby accounts are limited to daily cron jobs. This cron expression (0 * * * *) would run more than once per day. Upgrade to the Pro plan to unlock all Cron Jobs features on Vercel."
}
```

Fix: changed the cron schedule to run once a day instead of hourly, pushed, and deployments immediately started working again via git push as normal.

Would be great if this validation error could also surface in the dashboard / on git-triggered deployments and Deploy Hook responses, instead of only appearing via the CLI - it cost a lot of time to track down since every other signal (Git connection, GitHub App permissions, deploy hook response) looked healthy.