Workspace restricted (ToS violation) - deployments failing
Anonymous
FREEOP

a month ago

Description of the issue:

My workspace "Elegant-Tranquility" has been restricted with the reason "ToS violation". As a result, all build and deployment steps for my project are failing, even though the code itself is working correctly.

Error message:

"This deployment failed because the workspace for this project has been restricted, causing build and deploy stages to always start."

Project details:

  • Service: Song-Edit
  • Environment: Production
  • Project ID: 362ab459-4c2d-4ab4-a9b7-f2160ac3b1d3

I'm not aware of any billing issues, and I'm not sure which specific ToS violation this refers to. Could you please clarify the reason for the restriction and help me resolve it so my deployments can run again?

Closed

10 Replies

Railway
BOT

a month ago

We're not able to share the specifics behind why a workspace restriction was applied. This restriction cannot be lifted through any self-serve action such as upgrading or adding a payment method, and there is no data export path available while it is in place.


Status changed to Awaiting User Response Railway • about 2 months ago


Anonymous
FREEOP

a month ago

I completely understand you may not be able to share every detail, but I'd really appreciate any guidance you can give me so I don't repeat the same mistake in the future.

I run a personal Telegram music bot as a hobby project - it downloads/edits audio files (YouTube downloads, voice message editing, cover art, etc.). If something about this use case violates your Terms of Service, I'd genuinely like to know so I can avoid it going forward, rather than just guessing.

Could you at least point me to which category of the ToS this falls under (e.g. content policy, resource usage, prohibited use case)? I want to do this right and I don't want to violate your rules again.

Thank you for taking the time to look into this.


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

a month ago

We appreciate the thoughtful follow-up, but we're not able to narrow it down to a specific category or provide additional detail beyond what was shared. We understand that makes it harder to adjust, and we're sorry we can't be more helpful here.


Status changed to Awaiting User Response Railway • about 2 months ago


Anonymous
FREEOP

a month ago

I understand you can't reopen my account, and that's genuinely fine - I'm not asking for that. All I'm asking for is to understand what specifically went wrong, so I don't make the same mistake again with a future project.

Right now I feel a bit stuck: I have no idea what rule I broke, which means I could easily repeat it without knowing. That doesn't help either of us.

Is there any way this could be escalated to a supervisor or someone with more context who might be able to share even a general direction (not full details, just enough to avoid it next time)? I'd really appreciate it.

Thank you for your patience with me on this.


Status changed to Awaiting Railway Response Railway • about 2 months ago


Anonymous
FREEOP

a month ago

?


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

a month ago

We're still here. We've shared everything we're able to on this topic, and there isn't additional detail we can provide about the restriction or what triggered it.


Status changed to Awaiting User Response Railway • about 2 months ago


Anonymous
FREEOP

a month ago

?


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

a month ago

Nothing has changed on our end since the last message. We've shared everything we're able to on this topic.


Status changed to Awaiting User Response Railway • about 2 months ago


Anonymous
FREEOP

a month ago

lüge


Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

a month ago

Apologies, we only correspond in English. Please open a new thread in English.


Status changed to Closed Railway • about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...