3 hours ago
Escalate this to Railway technical support. Production environment b8350b5d-6ccb-41ca-92a1-0ed9c8dc52a7 contains hidden staged patch d3c5f1f6-96d3-4371-90a9-0a50df484044. The API reports 34 staged changes and an empty service configuration affecting all 15 variables, but the project dashboard shows no staged-change interface. Previous discard operations reported success but did not remove the patch. Do not deploy or accept it. Permanently delete the staged patch at the backend and verify through the service-configuration API that staged is null. Preserve current deployment 287919a8-5419-41b6-8da4-86cb25315b9c and all active variables.
1 Replies
2 hours ago
We checked your production environment just now and the staged change count is zero, meaning nothing is pending. Your current deployment is live with status SUCCESS and all 15 variables are committed and intact. The dashboard correctly shows no staged-change bar because it is driven by the change count, not by whether a patch record exists. Your discards did work: the patch contents are empty and the record the API returns is a normal, inert artifact that requires no backend deletion or staff intervention. If you have a deploy gate keyed on the existence of a patch record, gate on the change count inside the patch contents instead.
Status changed to Awaiting User Response Railway • about 2 hours ago