a month ago
Title: Railway workspace restricted during initial staging setup — will Hobby upgrade resolve it?
Hello Railway community,
I recently created a Railway account to deploy my SaaS application, a Staff Performance Evaluation System.
My workspace displays this warning:
“We limited this workspace after detecting unusual activity. It can't create new resources or deploy until it upgrades to a paid plan, which lifts this restriction automatically. Adding a payment method alone does not lift this restriction.”
I have created a staging environment and attempted to provision a MySQL database, but its build failed and the application service is still offline.
Before committing to a paid plan, I would appreciate clarification:
- Does upgrading from Trial to Hobby reliably remove this specific restriction?
- Could the failed MySQL service require additional action after upgrading?
- Is there any account verification required before I can deploy?
I am preparing a legitimate SaaS application for staging and would prefer to confirm the next steps before incurring hosting costs.
Thank you.
3 Replies
a month ago
Yes, upgrading the workspace to Hobby (or Pro) from the plans page lifts this restriction automatically. Adding a card alone won't do it, and you don't need any separate verification step on top of the upgrade.
The MySQL service didn't fail because of a build problem. Its deploy was refused by this restriction, which kicked in at the moment you added it. The service and its volume were still created. Once you've upgraded, you'll need to redeploy it, since a deploy that was refused doesn't retry on its own.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you for the response. My MySQL deployment still shows this diagnostic: “Contact Railway support to lift the restriction on your workspace, then redeploy the MySQL service.”
The deployment was blocked before initialization, and no redeploy button is available.
Could you please confirm whether upgrading this specific workspace to Hobby will remove the restriction, or whether a separate review is required? I would like to confirm this before incurring hosting costs.
Thank you.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This workspace currently shows as on the Hobby plan with no active restriction, so there is nothing further to complete on your side before deploying.
The message you're seeing comes from the staging MySQL deployment that was blocked earlier today. Another MySQL service in this workspace has deployed successfully since then, so deploying the staging MySQL service again should go through.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago