8 days ago
This appears to be the same "known lock state" described in a recent solved ticket where a staff member (angelo) confirmed it could not be resolved through the normal Deploy flow and had to be applied manually by the Railway team. My staged changes show the same behavior: clicking Deploy in the staged-changes panel does not clear the banner, and GitHub deploys / redeploys do not apply them. Could you please apply/reset the staged changes on this service from your side?
7 Replies
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
Very odd that this happened, i hit apply changes and its pending now. Let me know if you run into this again
Status changed to Awaiting User Response Railway • 8 days ago
8 days ago
.
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
Thanks for applying. However the banner still shows "3 Changes" pending after your apply — same locked behavior as before. I clicked Deploy on the staged-changes panel again and it still does not clear. Could you re-check and force the apply/reset from your side? It seems the staged changes are still stuck and not being committed to the environment.
Status changed to Awaiting Railway Response Railway • 8 days ago
Status changed to Awaiting User Response Railway • 7 days ago
7 days ago
On my side the service card still shows "Edited" with "3 Changes" even after reloading the page (screenshot attached). The staged changes are the deletion of SUPABASE_URL and SUPABASE_SERVICE_KEY plus a leftover. If you don't see them pending on your end, could the UI be out of sync? How do I get my dashboard to reflect the cleared state?
Attachments
Status changed to Awaiting Railway Response Railway • 7 days ago
Status changed to Awaiting User Response Railway • 7 days ago
6 days ago
Clearing the cache / hard reload did it — the pending changes are gone now. Thank you for the help, resolved.
Status changed to Awaiting Railway Response Railway • 6 days ago
Status changed to Solved gerandoimpulso-suporte2 • 6 days ago