6 days ago
Hi Railway team — urgent restore request.
What happened
Our live casino sandbox was wiped when the Railway trial ended / billing was not funded. We did not intentionally destroy the operation. After the project disappeared we can no longer open it in the dashboard (404), and player accounts / wallets / ledger are gone from our rebuild.
We also received a “Scheduled Volume Deletion” email for the original Postgres volume. The email template says “queued for deletion by someone on your team,” but the real trigger was trial/billing expiry — not an intentional wipe of our production sandbox.
ORIGINAL project (this is the one we need restored)
Dashboard URL still known (now 404 “Looks like you are lost”):
- Project name: desirable-emotion
- Project ID: 8ce8485e-ad37-41de-81be-f771e5302239
- Environment ID: a7c8e209-e531-4e3c-b1b7-972b8750e3fb
- Patch ID seen in URL: 3bd67ba6-3b04-4910-ba79-3ec36ab95d5e
- Workspace: eduardojonas244-star's Projects
- Workspace ID: 366b4ee7-0450-45a3-b58d-382ba2701da8
- Account email: eduardojonas244@gmail.com
This project hosted:
- casinha-sandbox (API) — api.ricaobet.com
- casinha-front-sandbox — www.ricaobet.com / ricaobet.com
- casinha-adm-sandbox — admin.ricaobet.com
- Postgres + volume postgres-volume (player accounts, wallets, ledger)
Volume deletion email evidence
- From: hello@notify.railway.app
- Date: Friday, July 31, 6:31 PM (local)
- Subject: Scheduled Volume Deletion
- Volume: postgres-volume
- Environment: production
- Project: desirable-emotion
- Message: volume queued for deletion; permanently deleted within 48 hours
- Email included a “Restore Volume” button
Please:
-
Confirm whether that Restore Volume link / soft-delete window can still be honored (or extended) given this was tied to trial expiry / billing teardown of a live operation.
-
Restore project 8ce8485e-ad37-41de-81be-f771e5302239 and/or its Postgres volume(s) from soft-delete / internal retention if anything remains.
-
Resend active Restore Project / Restore Volume links to eduardojonas244@gmail.com.
Related IDs in the same workspace (rebuild — do not confuse with original)
We rebuilt under a new project after the outage:
- Current project: positive-reverence
- Project ID: 97e4e572-fa41-4298-a858-7a1da1da1c60
- Environment ID: 9297cdd4-941b-441c-90ad-f7e084e25003
There is also a soft-deleted empty recreate (NOT the original):
- Project ID: 802ce642-40bb-4e20-a4d8-4f01b9f772ab
Please do not treat this empty project as the restore target.
In the rebuild we still have a volume remnant:
- Volume ID: 3ff7a25a-53a8-41e2-9f37-ce21b7b3c766 (postgres-volume)
- UI ~843MB used vs mounted empty PG18 ~47MB / 0 app tables
If you can recover a pre-teardown block image of the ORIGINAL volume from project 8ce8485e-…, please expose it.
Ask
Restore the original desirable-emotion project / Postgres volume (project ID 8ce8485e-ad37-41de-81be-f771e5302239). Lost due to trial expiry / automatic billing teardown — this ended our operation.
If nothing is recoverable, please confirm explicitly and state the retention policy for trial-expired projects and scheduled volume deletions.
Thank you — time sensitive (live player balances).
1 Replies
6 days ago
The original project (desirable-emotion) is no longer in our recoverable-deletion records, which means the deletion window has closed and neither the project nor its volumes can be restored from either side. We are not able to recover data from a project whose deletion window has passed. Your rebuild project (positive-reverence) is running normally on Pro with two active Postgres volumes.
Status changed to Awaiting User Response Railway • 6 days ago