a month ago
FreshCast production environment has an orphaned staged configuration patch that is visible through the Railway API but not in the Dashboard.
Patch ID: 1f39b11f-dd30-47d1-bb74-89f9f0876325
Environment ID: ae93c965-c936-4ae9-bd8d-54794c1b6740
Service ID: 2a07e359-a7b7-40c6-981e-cf1315b55588
environmentStagedChanges returns the patch as STAGED, with 23 changes, all removing production environment variables. The service reports live-with-staged-changes.
However, the Railway project canvas shows no staged-changes banner or Details panel, so there is no UI option to discard these changes.
We also attempted the Railway Agent's discard action. The Agent reported success, but subsequent independent API queries still return the same patch as active/STAGED.
All 23 live production variables remain present, so the patch has not been applied.
Could you please discard/delete this staged patch server-side without applying it or redeploying the service?
Please do not commit or deploy the staged changes, as doing so would remove all production environment variables.
3 Replies
a month ago
We checked the staged changes on that environment and the patch holds zero effective changes, so there is nothing to apply or discard. The dashboard correctly shows no staged-changes banner because it keys on the change count, not on whether a record exists. The empty patch record the API still returns is expected and benign, and no server-side cleanup is needed.
Status changed to Awaiting User Response Railway • 26 days ago
a month ago
Your discard did work. Patch 1f39b11f is stored empty on our side, and committing it would apply nothing, so your 23 production variables aren't at risk.
The 23 removals are a bug in the MCP read tools. They build their preview by diffing the patch against a copy of your live config with variable values masked out, and the masking makes every variable look like a pending removal even when the patch is empty. Your environment has 23 variables, so you see 23 changes. The dashboard counts the stored patch directly, which is why it shows no banner.
We've escalated this to the team that owns those tools. Until it's fixed, the dashboard and the environmentStagedChanges query are the accurate view, and the empty record can stay where it is.
25 days ago
This was a bug in how our API and MCP tools counted staged changes, and it is now fixed.
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago