a month ago
Limited Access
Deploys have been paused temporarily
Hello Railway Support Team,
I'm experiencing an issue with my Railway account.
My dashboard shows the following message:
"Limited Access — Deploys have been paused temporarily."
Because of this, I'm unable to deploy the latest updates to my Storevex Telegram Bot.
Could you please check my account and explain why deployments have been paused?
If there are any account restrictions, billing issues, or verification requirements, please let me know how to resolve them.
I would appreciate your help in restoring deployment access as soon as possible.
Thank you for your support.
5 Replies
a month ago
Apologies for the trouble. We had an incident that temporarily paused new builds for all workspaces, which has since been resolved, and there are no restrictions on your account.
Deploys triggered while builds were paused were not queued, so please trigger your Storevex bot deploy again. You can see the full timeline here: New builds are temporarily paused
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Apologies for the trouble. We had an incident that temporarily paused new builds for all workspaces, which has since been resolved, and there are no restrictions on your account. Deploys triggered while builds were paused were not queued, so please trigger your Storevex bot deploy again. You can see the full timeline here: [New builds are temporarily paused](https://status.railway.com/incident/JUA1PC5H)
a month ago
This is the same for me also.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Apologies for the trouble. We had an incident that temporarily paused new builds for all workspaces, which has since been resolved, and there are no restrictions on your account. Deploys triggered while builds were paused were not queued, so please trigger your Storevex bot deploy again. You can see the full timeline here: [New builds are temporarily paused](https://status.railway.com/incident/JUA1PC5H)
a month ago
Thank you for the update.
I have performed a hard refresh of the Railway Dashboard, but my Hobby workspace still shows:
"Limited Access – Deploys have been paused temporarily."
This warning appears across multiple services, including 4d-home-aggregator and 4d-polling.
My latest GitHub commit e449539 has not been deployed.
Since the incident has been marked resolved, could the Railway team please check whether my workspace is still affected by a deployment restriction?
Please also confirm whether this requires an account-side fix or whether deployment access will be restored automatically.
Thank you.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Apologies for the trouble. We had an incident that temporarily paused new builds for all workspaces, which has since been resolved, and there are no restrictions on your account. Deploys triggered while builds were paused were not queued, so please trigger your Storevex bot deploy again. You can see the full timeline here: [New builds are temporarily paused](https://status.railway.com/incident/JUA1PC5H)
a month ago
same problem not work redoply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
There are no restrictions on your account, so nothing needs to be fixed on your side. Shortly after our earlier reply we posted a separate notice about builds being paused for Free, Trial and Hobby workspaces. That notice has since been resolved, and builds for Hobby workspaces are running normally again: Builds paused for Free, Trial and Hobby workspaces.
Deploys triggered while builds were paused were not queued, so please trigger a new deploy of your latest commit for each affected service.
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
