23 days ago
Deploys paused on our production service since Oct 21, billing in good standing.
1 Reply
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
We paused new builds and deployments during the October 21 incident and turned them back on for all plans, including Hobby, on October 22. We don't see any restriction on your account. Running services kept serving their last successful deployment throughout.
Commits pushed during the pause weren't queued, so they won't deploy by themselves. Open the service, press Cmd+K (Ctrl+K on Windows) and choose Deploy Latest Commit, or push a new commit. Any variables you rotated during the pause also need a new deploy to take effect.
If you still see a "Limited Access" or "Deploys have been paused" banner, reload the dashboard or log out and back in. If the build fails with "unable to pull repository" or "build could not be started", that's because GitHub connections were revoked during the incident. To fix it, reconnect GitHub in Account Settings, check that the Railway GitHub App can still access the repository, then disconnect and reconnect the repository in the service's Settings and run Deploy Latest Commit. In a team project, the person who first connected the repository has to do the reconnect. There's more detail in our failing-deploys guide.
Status changed to Awaiting User Response dizzydes90 • 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