25 days ago
Subject: Staged patch cannot be discarded — project fbe64905-cf05-4c3c-b3a9-79fa8f5ca663, environment production ba589ee3-cb4f-4dba-8a9f-9270903650f0
Patch 204822ca-4c58-4897-a2d6-31c8212a1e7d (created 2026-09-06T18:28:30Z) shows 51 staged changes: every variable on services api (2219fbe0-f74e-4e9f-bec0-e914b738e8c6), backfill-oneoff (b17caf48-c84d-465c-8959-18176d12fc1f) and Postgres (154518c5-d38d-4521-8599-97339ab675ec) marked removed, Postgres deploy.multiRegionConfig.sfo.stackerAssignment removed, and three usage alerts (80/95/100%) added on volume baea71e8-ef0a-47d1-bdb4-4ff01d9fffc9. Nobody staged this intentionally, and applying it would delete every production variable.
Discard from the dashboard (2026-09-10 18:29Z) and from the Railway agent (2026-09-10 15:27Z) both reported success but only advanced the patch's updatedAt; all 51 changes remain. Please delete this staged patch entirely without committing any part of it. Nothing about the live services should change.
0 Replies
25 days ago
It looks like you already have a thread open about this: to Staged patch cannot be discarded (51 phantom variable removals). We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.
Status changed to Duplicate Railway • 25 days ago