a month ago
Hi, my account (kisu3528-alt, Hobby plan) shows "Limited Access — Deploys have been paused temporarily" on project carefree-empathy, service "web".
- Usage this period: $3.81 of the $5 included credit; a payment method is on file.
- What happened: the first deploy crash-looped because the start command came from a Procfile that Railway ran without a shell, so "${PORT:-8080}" was passed literally ("Error: Invalid value for '--port'"). Right after that, about 10 deploys were triggered in a row because I committed files one by one via the GitHub API.
- Both are fixed in the repo now (Procfile removed, railway.json with a shell-wrapped start command).
Could you please lift the restriction so I can redeploy? Thank you.
3 Replies
a month ago
Apologies for the trouble. There's no restriction on your account, and the crash loop and the run of deploys didn't cause the pause. We had an incident that paused new builds for all workspaces, and it was resolved on 2026-10-20 at 20:56 UTC.
Deploys triggered during the pause weren't queued, so please trigger a new deploy of your service to pick up your fixed start command. You can see the full timeline here: New builds are temporarily paused
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
my account is also showing "Limited Access — Deploys have been paused temporarily" and deploys are not running. I got a few deploys out since the earlier downtime, and now its back to paused.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Same issue for me. I can still not see any new deployments getting through. I pushed to main on GitHub and right away it doesn't pick it up. It just shows the yellow card "Limited Access — Deploys have been paused temporarily"
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month 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