#github

Pauline P. Narvas Welcome to the community, Justin! This is a great point. I've shared it with our team internally, hopefully we can get a workaround for you as soon as we can. 🙂

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Amy Egan Did you try the debugging tips linked above? I'd recommend checking the build settings and output to figure out why the page is missing

Cmarateaa 2510 can someone please answer

system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: Go to vercel.com/login Choose to sign in using the email + one-time password (OTP) option. Select Use another sign-in method Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yo

Amy Egan Hey there! Thanks for sharing the case number and for NOT posting your email. I found your case and confirmed it's assigned to the right team. It looks like the case was opened just a few hours ago, so escalation doesn't seem to be necessary here. Someone from the support team will reply soon

Amy Egan You've already ruled out a lot of possible causes. Thanks for sharing what you tried. If you still don't see any deployments triggered in the dashboard for new commits, then there's probably a configuration issue. There might be a note about a build error on the GitHub commit. Or you can test with the CLI by running vercel build to check for errors that would prevent a deployment from starting.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Albertoanibalmari Ship It Follow-up: I checked repo Settings → Webhooks → Recent Deliveries as suggested in a couple of related threads, and it's completely empty — no "Vercel" entry at all, broken or otherwise. Worth noting for anyone else landing here with the same idea: I believe this is actually expected, not a smoking gun. Our integration is via the Vercel GitHub App (confirmed earlier in this thread — granular permissions and "All repositories" access live under GitHub → Settings → Installations, not under repo-level Webhooks). GitHub Apps deliver events through a webhook registered once at the App level by the a

Muhehee Bumping this for the dev team's visibility. Since support confirmed this is an infrastructure bug but Hobby users can't open tickets, we really need an engineer to check this out. Our staging environment is still blocked.