Skip to content
Trial deployment restriction persisted after recovery — how to resolve?
randito05
OP

21 days ago

On October 23, our Trial project still displayed “Limited Access — Deploys have been paused temporarily” after the announced recovery. How can we check and resolve a persistent restriction without recreating the service or database?

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 21 days ago


21 days ago

There are no active restrictions on your account. The "Limited Access" banner came from the deploy pause during the October 21 incident, and deploys were restored for all plans, including Trial, on October 22.

If the banner is still showing, reload the dashboard or log out and back in. Commits pushed during the pause were not queued, so open the service, press Cmd+K (Ctrl+K on Windows) and choose Deploy Latest Commit, or push a new commit. Your existing service and database do not need to be recreated.

If a build then fails with "unable to pull repository", reconnect GitHub in your account settings, then disconnect and reconnect the repository in the service's Settings before deploying again.


Status changed to Awaiting User Response brody • 21 days ago


Railway
BOT

14 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 • 14 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...