N8n SaaS - workspace offline (503)

Questions
1

Describe the problem/error/question

My n8n Cloud workspace has been completely inaccessible for the past 2 day.
Whenever I try to log in, I receive a “Workspace offline (503)” error and cannot access the panel at all.

This is a critical issue because I actively rely on this workspace to run production workflows. Due to this downtime, I am unable to execute my automations and this has already resulted in financial loss.
I was previously informed that the issue might be related to community nodes.

I disable some workflows but the problem still happen.

I opened two tickets in support but is very slow (T-68671 and T-68656).

At this point, I urgently need my workspace access to be restored so I can continue running my workflows.

What is the error message (if any)?

Please share your workflow

Workspace offline (503)

Share the output returned by the last node

Not applicable – I cannot access the workspace to export or view workflows.

Information on your n8n setup

  • n8n version: 2.22.4 (Latest Stable)

  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default

  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud

  • Operating system: Not applicable (managed cloud environment)

2

Please reach out to help@n8n.io

3

@Lucas_Mioni_Bastos have u tried the restart option in ur app.n8n.cloud admin panel? thats the self-service force-restart for stuck pods, sometimes clears the 503 loop without waiting on support. on the community-nodes theory — which community nodes do u have installed and were any updated recently? a misbehaving community node OOMing on startup is a classic cause of a 503 that survives normal restart attempts because the pod keeps crash-looping before anything can load.

4

I did and put the number of tickets in my text :slight_smile:

but thanks!

5

Yes, I did restart in admin panel some times. They comeback but give 503 again in a feel minutes.

In support give me detail about consuptiom memory but i stopped every workflows and problem continue.

6

it has nothing to do with this but someone’s consultation took more than 48 hours to receive the key and nobody gives me an answer

7

hi @Lucas_Mioni_Bastos

please change Disable all community nodes back to its default and start the instance

image
image1043×805 39.6 KB

8

Done, but it’s still unresolved.

Support responded with a graph, but it doesn’t help identify which workflow is consuming so much memory.

I disabled the most recent workflows, but the problem persists.

Support escalated the issue and asked for another 2 days to respond.

image
image1478×522 56.2 KB