a month ago
What happened:
Our PostgreSQL service had two volumes both mounted at /var/lib/postgresql/data, which caused Postgres to fail with "Failed to create deployment". In an attempt to fix the conflict, I deleted one of the volumes via the volumeDelete GraphQL mutation. Unfortunately, I deleted the wrong one — the one containing our production data.
Deleted volume:
Volume name:
postgres-volume-vnwGVolume ID:
8b5062ae-8ae9-49f9-824c-1cf0a414ddebDeleted at approximately: 2026-04-13 ~20:40 UTC
Is there any possibility of recovering the data from the deleted volume 8b5062ae-8ae9-49f9-824c-1cf0a414ddeb? Even a block-level snapshot or backup from your infrastructure would be sufficient. Any restore point from before 20:40 UTC on April 13, 2026 would work.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 29 days ago
a month ago
(responding here as well - please avoid creating duplicate threads in the future.)
Unfortunately, the GraphQL volumeDelete mutation performs an immediate, permanent deletion without a grace period. As noted in our API documentation: "This will permanently delete the volume and all its data."
The 48-hour recovery window described in our Volumes documentation only applies to deletions made through the Railway dashboard UI. When you delete a volume through the UI, we queue it for deletion and send an email with a restoration link. The GraphQL API bypasses this safeguard and deletes immediately.
Status changed to Awaiting User Response Railway • 29 days ago
22 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 • 22 days ago