a month ago
When the “Wait for CI” option is enabled and a new environment variable is created in the Railway UI, the deployment waits indefinitely for a CI pipeline that does not exist.
As a result:
The deployment is stuck in a waiting state forever.
The deployment cannot be removed — even after deletion, it reappears automatically.
This makes the environment unusable.
I deactivated "Wait for CI" and started a new deployment, which stucks now too but at publishing Image..
Attachments
7 Replies
a month ago
same thing here
a month ago
same thing here, stuck somewhere in code snapshot or endlessly not building. I have no new variable, just a regular build from a commit
a month ago
I had one get through in my production environment, another in staging has frozen
a month ago
I was experiencing instability for the past hour or so, now I'm unable to push builds.
Attachments
a month ago
Same here 
a month ago
Builds and deployments were temporarily degraded. This has been resolved, and deployments should go out as normal. Status available here.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved christian • about 1 month ago