n8n - 💡(How to fix) Fix Self hosted n8n keeps offlining when an issue is happens [1 comments, 2 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#28447Fetched 2026-04-15 06:44:30
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
closed ×1commented ×1labeled ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

Is this normal behavior? In the logs there is no info but i would think that if there was an issue it would graceful stop the workflow. I have to kill the systemctl process and restart.

My n8n is self hosted btw.

To Reproduce

not possible. Self hosted. I can provide any info you request.

Expected behavior

The workflow should stop.

Debug Info

Debug info

core

  • n8nVersion: 2.8.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.22.0
  • nodeEnv: undefined
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: fe2e63d5-812d-4afe-a085-3f70feaa9f1c

storage

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

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

security

  • secureCookie: false

Generated at: 2026-04-14T08:02:18.368Z

Operating System

Debian 13

n8n Version

2.8.3

Node.js Version

v22.22.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The workflow not stopping as expected may be related to the concurrency setting or an issue with the self-hosted n8n setup, and restarting the systemctl process is currently the only known workaround.

Guidance

  • Review the concurrency setting in the n8n configuration, as it is currently set to -1, which may be causing issues with workflow stopping.
  • Check the system logs for any errors or warnings related to n8n or the systemctl process to gain more insight into the issue.
  • Consider setting up a test environment to reproduce the issue, if possible, to help identify the root cause.
  • Provide more information about the workflow and its configuration, as this may be relevant to the issue.

Example

No code snippet can be provided without more information about the workflow or n8n configuration.

Notes

The issue may be specific to the self-hosted setup or the version of n8n being used (2.8.3). More information about the workflow and system configuration is needed to provide a more accurate diagnosis.

Recommendation

Apply workaround: Restart the systemctl process, as this is currently the only known way to stop the workflow. This is not a permanent solution, and further investigation is needed to identify 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…

FAQ

Expected behavior

The workflow should stop.

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 Self hosted n8n keeps offlining when an issue is happens [1 comments, 2 participants]