I have this workflow causing a fatal error when it runs.
The workflow checks for invoices on my gmail, extracts the data from the file with Mistral OCR and saves the data in a google sheet.
In my previous instance (like one month ago) of n8n that was also running on Render, I never got any problem with the same workflow. In the Render logs I get this error :
“FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory”
After the error I also have an encryption key problem for my credentials.
Is there a change in the latest version of n8n that can cause this or has my workflow a flaw.
Hmm, so, we check logs abit further try see any patterns, such as counts of actions, processes open, or go depeer into the os, and see using top / htop, but there maybe another reason, it doesn’t seem that ure workflow, would cause a massive loop, and assume executions close quite quickly? Does it produce error again after some time when you restart?
Or how is it running atm?
It would be a env var can check on host, or if using dockers, likely there. What sort of file sizes process, you could look into using filesystem to reduce load.
Otherwise really you need to try look into why it happening such as monitoring to try see which part is taking it, and then look into that Memory-related errors | n8n Docs