n8n - 💡(How to fix) Fix Workspace going constantly offline [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29705Fetched 2026-05-05 06:03:10
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Timeline (top)
commented ×2subscribed ×2labeled ×1mentioned ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

What is the error message (if any)?

2 issues:

  • The workspace is constantly going offline. Not allowing proper work and publishing of workflows. See recording.
  • Running Out Of Memory in workflows that didn't before. example

I have tried everything: Restaring the workspace, updating to latest stable version, optimizing memory of code nodes, using datatables instead of writing in google sheets...

https://github.com/user-attachments/assets/78fd76cb-2d9a-434f-8bad-9574011c52b2

Please share your workflow/screenshots/recording

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.18.7
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-04T14:59:56.610Z

extent analysis

TL;DR

The issue can be mitigated by adjusting the concurrency setting and optimizing workflow memory usage.

Guidance

  • Review the workflow execution history to identify patterns or specific workflows that are causing the "Running Out Of Memory" issue, and optimize their memory usage.
  • Consider reducing the concurrency setting from 5 to a lower value to prevent overloading the system and causing the workspace to go offline.
  • Investigate the use of datatables and Google Sheets in the workflows to ensure they are not contributing to the memory issues.
  • Check the pruning settings to ensure that old executions are being properly cleaned up and not consuming excessive resources.

Example

No specific code snippet can be provided without more information about the workflows, but optimizing node configurations, such as reducing the number of nodes or using more efficient nodes, may help alleviate memory issues.

Notes

The provided information suggests that the issue is related to memory usage and concurrency, but more detailed analysis of the workflows and system resources may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Reduce concurrency setting and optimize workflow memory usage, as this is likely to provide the most immediate relief from the symptoms described, and further investigation can be done to identify and address the root cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Workspace going constantly offline [2 comments, 3 participants]