All workflows curropted after running out of space

Questions
1

Describe the problem/error/question

I ran out of space in my ec2 instance where im running my n8n workflows.
The day after that I checked my workflows as usually and ALL workflows were corrupt.
I increased the volume size and the file system of my instance but still every single one of my workflows are no longer usable.
I restarted the docker container but it didn`t work.

Is there any way to recover those corrupted workflows?

Thanks for your time!

What is the error message (if any)?

Install this node to use it

This node is not currently installed. It is either from a newer version of n8n, a custom node, or has an invalid structure

brave_screenshot (1)
brave_screenshot (1)464Ă—562 14.2 KB

brave_screenshot

Information on your n8n setup

  • n8n version: 1.44.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via: Docker
  • Operating system: Amazon Linux
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey @yang,

Welcome to the community :tada:

It looks like the workflows are still there, Have you tried updating to 1.51.0 and clearing your browser cache to see if that helps? Are you also using any community nodes?

1 Like
4

Hi, thanks for the quick response and welcoming me!

I cleared all site data and updated to the latest version but nothing changed unfortuantely.
Im not using any community node, every single node and trigger I used is corrupted.

I did more testing and i can not even add any trigger. I recieve this error when trying to add a trigger:
“triggerName” is an unknown node type

Aparently when running out of space my container got some corrupted files and messed up everything. I don`t want to be pessimist but from what i see i will have to remove the container and start all over again.

Any other possible solution is welcome :raised_hands:

Also, is there any good option to create backups of my workflows? It`ll be good to know.

Thanks.

5

Can you please try deleting the ~/.cache/n8n/ folder inside the container, and then restart the container.

1 Like
6

Hello.

Because of personal and time reasons I had to recreate the n8n container.

Thanks for your help and time!

1 Like
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.