Aqui está o post pronto para copiar e colar. Deixei em inglês porque o fórum do n8n é internacional e assim você recebe respostas de mais pessoas (incluindo engenheiros do n8n).
Onde publicar
Vá para https://community.n8n.io/ → faça login com sua conta → clique em “+ New Topic” → categoria “Questions” (é a mais ativa).
Título do post
Workspace offline (503) for 24+ hours - support not responding - production down
Conteúdo do post
Hi everyone,
I’m reaching out here because my n8n Cloud workspace has been completely offline for more than 24 hours, and my production workflows are down. I’ve opened a support ticket but only received an automated AI response so far, and a human agent has not yet replied despite the case being marked as urgent.
Hoping someone from the n8n team or the community can help, or at least confirm if anyone else is experiencing something similar.
The problem:
When I click “Open instance” from the Cloud dashboard, I get the “Workspace offline (503) - Your workspace is restarting and currently offline” screen.
However, in the Manage → Workspace status panel, the workspace is reported as “Online” running n8n@2.20.7. So there is an inconsistency between what the admin panel reports and what actually happens when trying to access the instance.
What I’ve already tried:
Clicked “Restart workspace” from the Manage panel multiple times, waiting 5–10 minutes after each attempt. No change.
Tried opening the instance from different browsers and in incognito mode. Same 503.
Checked the official n8n status page (https://n8n.statuspage.io/) — no global incidents reported.
Confirmed it’s not an execution limit issue (0/2500 executions this month).
Opened a support ticket via email to help@n8n.io more than 24 hours ago. Only received an automated AI response confirming the case was escalated to a human agent. No follow-up since.
Context:
The affected workflow has been running without any modifications for more than 4 months with zero incidents. The problem started suddenly, with no changes from my side.
My suspicion is that one of my workflows might be in an infinite loop or consuming too much memory, causing the instance to crash on every restart. I just need access to the editor for 10 minutes to disable the problematic workflow.
Descreva o problema/erro/pergunta
Qual é a mensagem de erro (se houver)?
Compartilhe seu workflow
(Selecione os nós na sua tela e use os atalhos de teclado CMD+C/CTRL+C e CMD+V/CTRL+V para copiar e colar o workflow.)
Compartilhe o resultado retornado pelo último nó
Informações sobre sua configuração do n8n
- Versão do n8n:
- Banco de dados (padrão: SQLite):
- Configuração EXECUTIONS_PROCESS do n8n (padrão: own, main):
- Executando n8n via (Docker, npm, n8n cloud, desktop app):
- Sistema operacional: