16 days ago
My workspace was restricted after hitting the concurrent build limit. The cause was an automated process committing data files to my GitHub repo roughly every 10 minutes with no watch paths configured, so every commit triggered a separate deployment and several builds ended up running concurrently. I have already added a watchPatterns config to railway.toml on main that limits builds to source files only, so this will not happen again. I just need the workspace restriction lifted so a fresh deployment can pick up the fix.
Fix already in place: railway.toml on main now sets watchPatterns = ["server.js", "dashboard.html", "package.json", "railway.toml"], which excludes the data/ directory that the automated commits write to. This prevents the build fan-out from recurring.
1 Replies
Status changed to Awaiting Railway Response Railway • 16 days ago
14 days ago
Unfortunately, workspace restrictions on paid plans are final and cannot be lifted, even when the underlying cause has been addressed. The path forward is to cancel the plan on this workspace from your billing settings, create a new workspace, and redeploy your services there. Your watch-path fix on main will apply automatically when you redeploy in the new workspace.
Status changed to Awaiting User Response Railway • 14 days ago
7 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 • 7 days ago