Hi n8n team & community,
I’m running into a pretty confusing issue with n8n Cloud and I’m hoping someone can help or confirm if this is a known problem.
Context:
Brand new n8n Cloud account
Workspace was created successfully
I upgraded my plan (payment completed, activation confirmed)
After the upgrade, the workspace never comes online
Current state:
Workspace shows as OFFLINE
No error messages shown anywhere
I restarted the workspace more than 10 times
Activation process is confirmed as completed
Admin Panel shows no obvious errors
All n8n services are reported as operational
Support interaction so far:
AI support keeps looping on “please complete activation”
I have confirmed activation multiple times
Screenshots of the Admin Panel were already provided to support
Ticket has been escalated to a human, but no response yet
Suspicion:
It feels like this might be a backend / database provisioning issue, especially since:
This is a brand new account
The issue started immediately after upgrading the plan
There are no user-facing errors at all
Questions:
Has anyone experienced a Cloud workspace stuck offline after a plan upgrade?
Are there known database or provisioning delays/issues that can cause this?
Is there anything I can check or trigger manually on my side?
At the moment I’ve paid for the upgrade but can’t access my workspace at all, which is pretty frustrating.
Any insights from n8n staff or other Cloud users would be highly appreciated.
Thanks in advance
Unfortunately, after more than 24 hours without a working workspace or a concrete resolution, I have to seriously reconsider relying on n8n Cloud.
At this point I’m forced to either:
switch to another hosted automation service, or
fall back to the local / self-hosted version
The concerning part is not just the delay, but the fact that:
this is a brand new n8n Cloud account
the plan upgrade was completed successfully
and yet the workspace never came online at all
If a freshly created Cloud workspace cannot start reliably, it raises serious concerns about how safe it is to depend on the hosted service for production workloads without visibility into errors or recovery options.
I’m still open to resolving this and continuing with n8n Cloud, but right now the experience is unfortunately a very bad first impression.
If someone from the n8n team can look into this on the backend side (provisioning / database / workspace bootstrap), I’d really appreciate it.