25 days ago
Project: india-ai-financial-analyst (faaeb5ad-425e-4a7d-b264-c4c56982890b)
Environment: production (1c6fde7d-3e37-40fa-ae30-415ddbcac967)
Patch ID: db30a916-94ef-4354-b2f2-463eace5ada4
There is a staged changes patch on our production environment with 124 changes that deletes shared and per-service variables (DATABASE_URL, SUPABASE_URL, PORT, and all ENABLE_* flags) across all 5 services (api, research-worker, official-feed-worker, live-market-worker, yfinance-backfill-once). We do NOT want to apply/commit this patch - we want it discarded/cleared without deploying.
Issues we've hit:
- The dashboard canvas for this environment does not show the "staged changes" banner described in your docs, even after hard refresh, despite the patch existing and being confirmed via the public API (environmentStagedChanges query returns status: STAGED for this patch id).
- The public GraphQL API has no discard/cancel mutation for staged patches - only stage, commit/apply, and preview operations exist, and the EnvironmentPatch status enum only supports STAGED/APPLYING/COMMITTED/FAILED, with no "discarded" terminal state.
- We used the in-dashboard AI Agent to ask it to discard this exact patch on three separate occasions over the past ~12 hours. Each time it replied confirming the patch was discarded and staged changes were now zero - but as of this report, the same patch ID with the same 124 changes is still status: STAGED. The agent's success confirmations appear to have been false.
Could you please manually clear/discard this staged patch on our production environment, and let us know if there's a supported way to do this ourselves going forward? We want to avoid ever clicking "Deploy" on it, since it would delete these critical variables in production.
Thank you.
1 Replies
25 days ago
Your production environment currently has zero staged changes, so none of those 124 variable deletions are pending and nothing destructive will be applied on deploy. The patch record still appearing via the API with status: STAGED is normal. The dashboard correctly shows no staged-changes banner because it is driven by the change count in the patch contents, not by the existence of the record or its status field. For managing staged changes via the API going forward, the Manage Environments docs cover the available staging operations.
Status changed to Awaiting User Response Railway • 25 days ago
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