Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Navigating to the Executions tab and looking at failed executions takes the whole workspace 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#29615•Fetched 2026-05-02 05:46:31
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
MarcoKuuskMarcoKuusk
Participants
JoffcomJoffcomMarcoKuuskMarcoKuuskn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×2labeled ×2mentioned ×2subscribed ×2

Error Message

Describe the problem/error/question

What is the error message (if any)?

error 503 as soon as I look at a failed execution.

  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Navigating to the Executions tab and looking at failed executions takes the whole workspace offline. As soon as I navigate to a failed execution the whole workspace goes offline. It is indicated by yellow triangle and text offline in the upper right corner of the UI. After reloading page the whole worksapce is offline for a minute or two.

What is the error message (if any)?

error 503 as soon as I look at a failed execution.

### core

- n8nVersion: 2.18.4
- 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 (windows nt 10.0; win64; x64; rv:151.0) gecko/20100101 firefox/151.0
- isTouchDevice: false

Generated at: 2026-05-01T09:59:09.357Z

extent analysis

TL;DR

The issue may be related to the concurrency setting or the pruning configuration, causing the workspace to go offline when navigating to failed executions.

Guidance

  • Check the concurrency setting (concurrency: 5) to ensure it's not overwhelming the system when loading failed executions.
  • Verify the pruning configuration (pruning.enabled: true) to see if it's causing issues with data retrieval or storage.
  • Investigate the error 503 message to determine if it's related to a server-side issue or a client-side problem.
  • Consider temporarily disabling pruning or adjusting the concurrency setting to see if it resolves the issue.

Notes

The provided information suggests a potential issue with the system's ability to handle concurrent requests or retrieve data from storage. However, without more detailed logs or error messages, it's difficult to pinpoint the exact cause.

Recommendation

Apply workaround: Temporarily adjust the concurrency setting or disable pruning to see if it resolves the issue, as this may help mitigate the problem without requiring a full system upgrade or configuration change.

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…
#dependency conflict#environment setup#docker error#permission error#memory optimization

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 Navigating to the Executions tab and looking at failed executions takes the whole workspace offline [2 comments, 3 participants]