Failed staged-changes workflow blocking production environment
josuechavando350-png
FREEOP

25 days ago

Project: seo-avengers-200-backend

Environment ID: 1cae2f40-91a8-4d66-89a7-438d73c4a364

Failed workflow ID: 97d89e9c-2423-4386-84f6-8faf34ee1d9d

A staged-changes commit workflow failed and the production environment is now blocked. Further changes return:

Cannot modify patch with status FAILED (must be STAGED)

Please clear/reset the failed staged-changes workflow so I can continue deploying a persistent volume and Redis for the semantic-python-nlp service.

Please do not delete or recreate the environment.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway • 25 days ago


Railway
BOT

25 days ago

The deploy was refused because the staged volume size (2048 MB) exceeds the Trial plan's 500 MB volume storage cap, which is the error the platform returned when the changeset was applied. The environment is not locked: a refused apply is terminal on that specific changeset, and the environment accepts new changes immediately. To proceed, you would need to reduce the volume size to 500 MB or less, or upgrade to a paid plan (Hobby allows up to 5 GB per volume). Your workspace is also at the Trial plan's 3-volume-per-project limit, so adding both volumes in the current project will require a plan upgrade as well.


Status changed to Awaiting User Response Railway • 25 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...