23 days ago
Hello Railway Support,
I am experiencing an environment-level patch issue in my Railway project that is preventing me from creating new resources.
Project: QV-001 Investment Lab
Environment: production
Environment ID: 66b390f3-5033-4ed9-853a-6888f0ba1d22
The affected workflow/patch is:
commitChanges/66b390f3-5033-4ed9-853a-6888f0ba1d22/6962f1a8-0741-44b2-9b25-c015ae618dbf
The error being returned is:
Cannot modify patch 6962f1a8-0741-44b2-9b25-c015ae618dbf with status FAILED (must be STAGED)
The issue started while I was trying to create separate infrastructure for my own PostgreSQL logical backups using pg_dump. I am currently on the Hobby plan, so I understand that Railway's managed Backups and Point-in-Time Recovery (PITR) features are only available on the Pro plan.
However, I am not trying to enable Railway's managed Pro backup feature. I am trying to create my own backup solution using separate resources.
After the failed patch, the environment appears to be locked and attempts to create new resources such as a bucket, volume, function, or service are blocked.
My production PostgreSQL service is currently online and has not been modified or restored. I do not want any changes made to the production database or its existing volume.
Could you please:
- Check why this patch/workflow entered the FAILED state.
- Reset or clear the failed patch state so that I can create resources again.
- Confirm whether Hobby plans are allowed to create their own PostgreSQL logical backup solution using pg_dump and separate storage/resources.
- Confirm whether the failure is related to a Hobby plan limitation or is simply a stuck/failed environment patch.
Please do not reset, delete, restore, or modify my production PostgreSQL database or its existing volume while investigating this issue.
Thank you.
1 Replies
23 days ago
The volume creation was rejected because it requested 20 GB, but the Hobby plan caps total volume storage at 5000 MB and your workspace has already used that full allowance. Your environment is not locked. The error you're seeing is from a stale reference to the earlier operation. You can dismiss the failed operation using the overflow menu on the deploy bar in your project canvas, and then create new resources as usual. You're free to build your own pg_dump backup solution on Hobby, but you won't be able to add another volume until you free existing volume capacity or upgrade your plan.
Status changed to Awaiting User Response Railway • 23 days ago
16 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 • 16 days ago