an hour ago
Hello Railway Support,
Project: mixiri-logistics-staging
Project ID: 58232109-5f89-4d12-ae27-7e00696d7c61
Environment: staging
Environment ID: bb2f211b-a712-4dd5-9622-aa1123233983
The Public API / environmentStagedChanges returns one EnvironmentPatch with status STAGED, but the Railway canvas shows:
- no staged-changes banner;
- no change count;
- no purple New/Edited/Removed card;
- no Details button;
- no supported per-change discard control.
The identifier has been retained privately; its SHA-256 is:
80852ffca8497a651fbbecfbfe9d086df79e3fbfa5cde7fa331402478e545996
Current services that must be preserved:
- logistics-api-staging
- logistics-postgres-staging
- logistics-backup-staging
- logistics-backup-eu-staging
- logistics-migration-staging
- logistics-provision-staging
Current volumes that must be preserved:
- logistics-postgres-staging-volume
- logistics-backup-staging-volume
- graceful-volume
All protected services are currently healthy/successful. No production is involved.
Please:
- identify the exact non-sensitive content/resource/action represented by this STAGED object;
- confirm whether it is an orphaned/stale patch;
- provide or execute the supported method to discard only this invisible patch without applying it;
- do not deploy, delete, restore, resize, move, or modify any service, volume, variable, region, replica, database, or production resource.
We will perform a read-only inventory after your response. Please do not request or post any token, password, private key, database URL, or variable value.
Thank you.
2 Replies
an hour ago
The environmentStagedChanges query is non-nullable and always returns an EnvironmentPatch object, even when nothing is staged. The record you are seeing (with status: STAGED and appliedAt: null) is the query's empty-response shape, not an orphaned or stale patch. Its contents are empty, which means zero staged changes exist in this environment. The dashboard is correct in showing no banner, no change count, and no discard control. All six services in your staging environment are deployed and healthy, and no action is needed. If you want to confirm programmatically, read the change count inside the patch contents rather than status or appliedAt.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
The `environmentStagedChanges` query is non-nullable and always returns an `EnvironmentPatch` object, even when nothing is staged. The record you are seeing (with `status: STAGED` and `appliedAt: null`) is the query's empty-response shape, not an orphaned or stale patch. Its contents are empty, which means zero staged changes exist in this environment. The dashboard is correct in showing no banner, no change count, and no discard control. All six services in your staging environment are deployed and healthy, and no action is needed. If you want to confirm programmatically, read the change count inside the patch contents rather than `status` or `appliedAt`.
an hour ago
Separate clarification — no action requested:
Railway sent us an “Upcoming Volume Deletion” email for a temporary staging volume. It says the volume is queued for deletion, will be permanently deleted within 48 hours, and remains restorable during that period.
Could Railway please confirm:
- Is the deletion request already accepted, with no additional Deploy, Apply, or Delete action required?
- Is it normal for the volume to remain visible and restorable during the retention window?
- If “Restore Volume” is not used, will Railway purge it automatically within 48 hours?
- Which read-only UI or API status proves that the permanent purge is complete?
This is a clarification request only. We do not authorize any operation or modification. No project, service, volume, credential, URL, variable, or other secret is identified here.
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 hour ago