a month ago
I have a stale staged patch in a Railway production environment that cannot be discarded.
The dashboard "Discard Changes" removes newly staged edits, but the existing stale patch remains.
Railway's discard staged changes operation also reports success, but a canonical configuration read still reports the same staged patch with existing service variable names.
The live variable values must NOT be changed or deleted.
This stale patch also prevents me from safely enabling "Wait for CI" / source.checkSuites, because enabling it gets added to the existing stale patch instead of becoming an isolated change.
Has anyone seen this before, or can Railway staff help clear the stale staged patch without applying it and without redeploying the service?
Please do not suggest applying the staged changes, because their contents cannot be safely verified.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 26 days ago
25 days ago
This was a bug in how our API and MCP tools counted staged changes, and it is now fixed.
Status changed to Awaiting User Response Railway • 25 days ago
20 days ago
Terimakasih
Status changed to Awaiting Railway Response Railway • 20 days ago
Status changed to Solved brody • 20 days ago