I need this account reviewed for repeated Production environment/config issues.
Over multiple setup attempts, environment variables in Vercel have behaved inconsistently. Variable names appear in Production, but runtime availability has not been reliable. We have had to remove and re-add secrets multiple times before the application could actually read them.
This has affected multiple integrations, including:
- Stripe
- Vapi
In practice, this has meant:
- API keys had to be hand-installed repeatedly
- redeploys did not always reflect expected env changes immediately
- dashboard state and runtime behavior did not consistently match
- production troubleshooting had to be done through live runtime checks rather than trusting the dashboard
There was also an issue with the support widget itself during troubleshooting, where sending a message required selecting an emoji reaction, but no emoji could be selected.
This has caused repeated delays in getting production integrations stable.
Please review this account/project for:
- Production environment variable persistence
- config propagation into deployments
- dashboard/runtime mismatch for env values
- any account-level issue affecting secret handling
I’m not asking for general guidance. I’m asking for an actual review of the account/project behavior, because this has happened repeatedly across more than one integration.