I’m unfortunately not seeing any big red flags here that might point to an issue. The builds are running properly and are tagged as production and there is no cache being used here
You seem to have two separate Vercel projects set up currently, one for production and one for staging. Is there any chance you’re checking the “production” project’s variables while the separate project you’re using for staging is left on the old values?
The idiomatic way to do this would be to have a single project and go to Settings -> Environments to set up a custom staging environment tagged to the staging branch with its own domain, which will ensure they all stay in sync
Unfortunately I have very limited visibility into your current environment variable structure (for security reasons) so I can’t check on your behalf, but I wonder if there’s a bug where the branch named “staging” is triggering a heuristic that causes it to use Preview environment variables instead? That would seem strange to me but everything else looks correct
If your production project appears to be working correctly, I’d recommend consolidating them as I’ve outlined above and then if you run into the issue again you should be able to notice exactly when it happens for diagnosis