Project: sovereign-budget (Hobby plan), connected via the Vercel GitHub App integration.

The issue: an automatic push to main occasionally produces no deployment at all in the Deployments tab — not a failed build, nothing. It's happened at least 3 times now over the past couple weeks, not a single fluke.

What I've already ruled out:

• Not a GitHub delivery problem — the push itself reaches GitHub every time (confirmed via git log on origin/main and checking the commit on GitHub directly).
• Not a commit-author-verification issue — I compared two consecutive commits: 7de5679 deployed normally, the very next commit, ccb099b, silently didn't. Both have the identical commit author (marcowieczka-spec marcowieczka@gmail.com). Since the author is the same on both, an unverified/mismatched email can't explain why only one of them was dropped.
• Not the build itself failing — manually triggering a Deploy Hook for the exact same commit that was silently skipped deploys it successfully every time, with zero changes needed.

Pattern I've noticed (not confirmed as the cause, just an observation): the miss seems to happen on a push that follows shortly after a previous push just deployed successfully — i.e., two pushes close together, where the first one works and the second one silently doesn't.

What I'm hoping someone can help with:

• Has anyone else seen this exact symptom — a push event that GitHub definitely sent, but Vercel never even shows a failed/skipped deployment record for?
• Vercel's own support AI suggested this could be build-queuing/job-supersession behavior (a later commit's build implicitly cancelling an in-flight one) or an Ignored Build Step filter — but I don't have an Ignored Build Step configured, and the two problem commits weren't pushed that close together (a few minutes apart, not simultaneous). Does anyone know if there's a known issue in this space?

I don't have access to the actual webhook delivery logs myself (GitHub only exposes those to the app owner, not installers), so I can't confirm what happened on Vercel's end for the dropped commit — just what I can observe from the outside. Happy to provide more detail (exact timestamps, commit SHAs, project ID) if it helps someone dig in.