All new builds break - issue on Vercel side (PRO account)

Help
1

Anyone else getting this issue with all new builds? I have created a support ticket (though that even took 5 or 6 tries to actually generate).

I’m experiencing a critical issue where all new builds are breaking at runtime, even when deploying code that is byte-identical to my last known-good production deployment (commit 32633a7). The builds complete successfully and show READY status, but the deployed functions fail at runtime, returning unstyled HTML instead of expected JSON responses from my Express application.

I’ve conducted extensive bisection testing and confirmed this is not a code issue:

  • Content-identical pushes to the known-good commit produce broken functions

  • Changing Node.js versions (24.x → 22.x) didn’t resolve it

  • Build logs show no errors; dependencies and binary deps compile successfully

  • The issue persists across all new deployments regardless of code changes

This pattern strongly suggests an infrastructure-level environmental drift at Vercel between when my known-good deployment was created and now. My production deployment (32633a7) remains functional when manually promoted, but all new deployments fail at function execution time.

2

If you’re having trouble deploying an Express app, this guide can help.

You can also ask v0 for suggestions tailored to your own project setup.

3

@nhbean123 Check your runtime logs. The error logs indicate your new deployments started missing a few environment variables

Missing required environment variables: STRIPE_PRICE_BASIC_MONTHLY, STRIPE_PRICE_DIGITAL_BOOK

and based on your account activity logs, you seem to have removed those env vars recently

4

I validated in many different ways that this, and many other potential causes, were not the issue.