a month ago
▎ Since 2026-10-20 17:05 UTC both services in my project went offline and I can't redeploy. Postgres logged a clean shutdown; all deployments now show status REMOVED.
▎
▎ railway up uploads successfully, then returns "Deploys have been paused temporarily." I've retried six times over several hours.
▎
▎ What's odd: my account looks healthy from every angle I can check. Hobby plan is active on the Plans page, and the GraphQL API reports my workspace as banReason: null with customer.state: ACTIVE. The status page shows no incidents.
▎
▎ So the restriction appears stuck rather than warranted. My Postgres volume still reports state READY, but I can't export anything while the service is down.
▎
▎ Happy to DM my project and workspace IDs to anyone from the team who can take a look.
8 Replies
a month ago
Two separate things happened here. Your services went offline at 17:05 UTC when your trial ended, which is what stopped them and marked those deployments REMOVED. Your Hobby plan started at 18:47 UTC, after that.
The "Deploys have been paused temporarily" error came from an incident that paused new builds across all workspaces while you were retrying, not from a restriction on your account. That incident has since been resolved and builds are running normally again: New builds are temporarily paused. Deploys attempted during the pause were not queued, so they need to be triggered again.
Your Postgres service still has its volume attached. Bring it back first by opening the service, pressing CMD + K (CTRL + K on Windows and Linux) and running "Redeploy source image". Redeploying does not delete or reset the volume's data. After that, run railway up again for your web service.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Two separate things happened here. Your services went offline at 17:05 UTC when your trial ended, which is what stopped them and marked those deployments REMOVED. Your Hobby plan started at 18:47 UTC, after that. The "Deploys have been paused temporarily" error came from an incident that paused new builds across all workspaces while you were retrying, not from a restriction on your account. That incident has since been resolved and builds are running normally again: [New builds are temporarily paused](https://status.railway.com/incident/JUA1PC5H). Deploys attempted during the pause were not queued, so they need to be triggered again. Your Postgres service still has its volume attached. Bring it back first by opening the service, pressing CMD + K (CTRL + K on Windows and Linux) and running "Redeploy source image". Redeploying does not delete or reset the volume's data. After that, run `railway up` again for your web service.
a month ago
It's saying that Postgres and web are both "offline". How do I get everything running again?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Both services still show "offline" because their latest deployments are still in the REMOVED state, and nothing has been deployed since builds came back, so each one needs a new deployment.
Start with Postgres: open the service, find its most recent deployment in the deployments list, open the three-dot menu on it and choose Redeploy. That creates a new deployment with the same configuration, and your volume stays attached to the service.
Once Postgres is running, do the same for web. You can also run railway redeploy from the CLI for that service, or run railway up again if you want to deploy your local code.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Both services still show "offline" because their latest deployments are still in the REMOVED state, and nothing has been deployed since builds came back, so each one needs a new deployment. Start with Postgres: open the service, find its most recent deployment in the deployments list, open the three-dot menu on it and choose Redeploy. That creates a new deployment with the same configuration, and your volume stays attached to the service. Once Postgres is running, do the same for web. You can also run `railway redeploy` from the CLI for that service, or run `railway up` again if you want to deploy your local code.
a month ago
still nothing is happening.. I need my all in one CRM up and running and I need your help
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your Postgres service is running again. Its new deployment finished successfully at 22:03 UTC and still has its volume attached.
The web service is the one still offline. Its latest deploy, started at 22:06 UTC, failed before it could build, at the step where we take a snapshot of your code, with the error "Failed to create code snapshot. Please review your last commit, or try again." Because it never got past that step, no container was started.
To get web running, trigger a new deploy for that service. You can open web, find that failed deployment in the deployments list and choose Redeploy from its three-dot menu, or run railway up again from your project folder. If the same snapshot error comes back on the retry, check the most recent commit on the CRM repository the service deploys from, since that error points at the code being snapshotted.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Postgres came back up on its own at 22:03 UTC and is accepting connections normally. Only the web service deploy is affected — railway up reaches "Uploading..." then times out after ~95s, every attempt, while the GraphQL API responds in 0.5s from the same machine.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your web service's most recent deploy, created at 22:38 UTC, failed at the code snapshot step after about two minutes with "Failed to create code snapshot. Please review your last commit, or try again." It never reached the build, so no container was started. The ~95s upload timeouts you're seeing come before that step, so those attempts don't create a deployment at all.
railway up compresses and uploads your current directory. It skips .git, node_modules, and anything in your .gitignore or .railwayignore, so it's worth checking those files cover any large local folders. Running railway up --verbose shows more detail on where the upload stops. More on file handling is in the railway up docs.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
still this problem is occuring i still face 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