# Error: Execution stopped at this node... may have run out of memory **URL:** \ **Category:** Questions\ **Created:** [June 19, 2025, 5:57pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438 "2025-06-19T17:57:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![redsef\_ENJRI1](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/redsef_enjri1/32/58716_2.png) [@redsef\_ENJRI1](https://community.n8n.io/u/redsef_ENJRI1)\ **Post date:** [June 19, 2025, 5:57pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/1 "2025-06-19T17:57:12Z")
I have an issue after the latest 4 updates where scenario crushes with this error: Execution stopped at this node… may have run out of memory ## What is the error message (if any)? error: Execution stopped at this node… may have run out of memory ## Please share your workflow ## Share the output returned by the last node ## Information on your n8n setup - **n8n version:** 1.97.0 - **Database (default: SQLite):** postgresql - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** did not get this one ? - **Running n8n via (Docker, npm, n8n cloud, desktop app):** self hosted VPS - **Operating system:** Linux ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [June 19, 2025, 6:04pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/2 "2025-06-19T18:04:28Z")
Hey @redsef_ENJRI1 hope all is well. Have you read this article? > **[Typical causes - Memory-related errors | n8n Docs](https://docs.n8n.io/hosting/scaling/memory-errors/#typical-causes)** > > n8n doesn't restrict the amount of data each node can fetch and process. While this gives you freedom, it can lead to errors when workflow executions require more memory than available. This page explains how to identify and avoid these errors. |... ---
**Author:** ![redsef\_ENJRI1](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/redsef_enjri1/32/58716_2.png) [@redsef\_ENJRI1](https://community.n8n.io/u/redsef_ENJRI1)\ **Post date:** [June 19, 2025, 6:09pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/3 "2025-06-19T18:09:39Z")
@jabbson Yup read it and applied every single recommendation. I saw many people having saw issue lately if I am not mistaken after latest updates. ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [June 19, 2025, 6:14pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/4 "2025-06-19T18:14:34Z")
Assuming you have tried this as well then? > **[Enable filesystem mode - Scaling binary data in n8n | n8n Docs](https://docs.n8n.io/hosting/scaling/binary-data/#enable-filesystem-mode)** > > Binary data is any file-type data, such as image files or documents generated or processed during the execution of a workflow. | How to handle large files without degrading n8n's performance. ---
**Author:** ![redsef\_ENJRI1](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/redsef_enjri1/32/58716_2.png) [@redsef\_ENJRI1](https://community.n8n.io/u/redsef_ENJRI1)\ **Post date:** [June 19, 2025, 6:25pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/5 "2025-06-19T18:25:12Z")
I do not have the N8N\_DEFAULT\_BINARY\_DATA\_MODE in environment variable. this is my environment variable: environment: - SERVICE\_FQDN\_N8N\_5678 - ‘N8N\_EDITOR\_BASE\_URL=${SERVICE\_FQDN\_N8N}’ - ‘WEBHOOK\_URL=${SERVICE\_FQDN\_N8N}’ - ‘N8N\_HOST=${SERVICE\_URL\_N8N}’ - ‘GENERIC\_TIMEZONE=${GENERIC\_TIMEZONE:-Europe/Berlin}’ - ‘TZ=${TZ:-Europe/Berlin}’ - DB\_TYPE=postgresdb - ‘DB\_POSTGRESDB\_DATABASE=${POSTGRES\_DB:-n8n}’ - DB\_POSTGRESDB\_HOST=postgresql - DB\_POSTGRESDB\_PORT=5432 - DB\_POSTGRESDB\_USER=$SERVICE\_USER\_POSTGRES - DB\_POSTGRESDB\_SCHEMA=public - DB\_POSTGRESDB\_PASSWORD=$SERVICE\_PASSWORD\_POSTGRES Also if this may help: I had Ai agent node where it blocked, just changed to Basic LLM chain and still same issue. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [September 17, 2025, 6:25pm UTC](https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/135438/6 "2025-09-17T18:25:20Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.