No Access to "Open Instance" Workspace offline (503)

Questions
1

Describe the problem/error/question

I’m going to give this a try since I can’t get a response from anybody but the automated reply feature. A few weeks ago I received an email:

This is the n8n cloud team.

We are contacting you because our engineering team has noticed repeated unscheduled restarts of your n8n cloud instance. After reviewing the available logs around these restarts, it appears that your instance has experienced a number of out-of-memory issues.

To allow your instance to restart and prevent it from crashing again, the team has disabled the active workflows with the IDs “[workflow0],[workflow1],[workflow2],[workflow3,[workflow4],[workflow5],[workflow6]” on your n8n Cloud instance.

Firstly, We’d like to apologise for the inconvenience this is causing. We do not have direct access to your workflows, so we cannot confirm what exactly is causing the out-of-memory situation in your case. You may want to take a look at our documentation on memory related errors, which lists a number of possible causes and approaches to avoid them.

Click Here to find out more

We hope this has provided some clarification as to what has happened here. Please accept our sincere apologies for any inconvenience this may cause and please let us know if you have any further questions on the above.

n8n Support

This was Christmas Eve so I was not looking at my emails, and by the time I did, a lot of junk emails had nudged this down to the bottom. I do remember logging into my instance and wondering why everything was off. It baffled me and made me wonder how long it had been that way. So I simply turned it back on and went back to business. A couple of days later, it was off again. The difference now is that I cannot access my instance. Only the dashboard. I can’t get in to diagnose nor fix the out-of-memory situation. I told the automated reply to shut down any running workflows and it stated that it could, but I still cannot log in.

What is the error message (if any)?

image
image1490×722 79.3 KB

After clicking “Open Instance”

image
image597×426 13.9 KB

Please share your workflow

n/a

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

n/a

Information on your n8n setup

  • n8n version: [email protected]
  • Database (default: SQLite): ?
  • n8n EXECUTIONS_PROCESS setting (default: own, main): n/a
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows XP
2

I need to post an update as this issue I feel like was mostly my fault. Christmas Eve, I got an email that I was not aware of. The n8n team simply disabled all of my workflows but I still had access to my instances. That was my chance to fix the issue. Instead, I turned all of my workflows back on and once I hit the memory limit again, my instance got shut down and was inaccessible. I chatted with the auto-reply, but upon requesting a human representative, they responded within about 2 days. Once again, I did not see this email until about 3 days later. After 4 days, my instance was available again for me to access it to fix the issues that continously caused it to get shut down.

So, in conclusion, and also in my humble opinion because your issues my be different:

1 - Check your email for communications first if your workflows ever seem to cut off by themselves
2 - Do not expect in instant reply, however, the speed was not unreasonable. I’m sure there are more users than there are staff, and this is high tech stuff we’re working with