Project: plum-works-platform Account/workspace: simonmeighan-3850 (Hobby) GitHub repository: simonmeighan-rgb/Plum-works-platform (private) Production branch: main GitHub-triggered deployments and Deploy Hooks have started intermittently failing to create deployment records. Last successful automatic deployment was commit 5e31877f7a2884177e5a990e0e52365cb55a59d0. I refreshed the GitHub authentication in Vercel as advised by Vercel support. After doing that, the existing Owner DEV main Deploy Hook successfully created two Production deployments for commit 424e13dac9776b680271f12c844d5609377f0601. This demonstrated that Vercel could fetch the private repository. Those deployments reached the build stage but failed because of a CSS syntax error in the application. I fixed that application error and pushed commit 667a617283a1bffbe620b29f3ec8fb960578459d to main. However, the GitHub push for 667a617 did not create a Vercel deployment. I subsequently triggered the same Deploy Hook again, but that also did not create a deployment record. Both Both the GitHub commit-author email and the email associated with my Vercel account are verified in Vercel. This therefore appears to be intermittent deployment-trigger processing rather than an application build failure: the hook successfully generated deployments for 424e13d, but neither Git nor the same hook generates a deployment for the subsequent 667a617 commit. Can someone from Vercel please investigate why deployment jobs are intermittently not being created for this project/ref?