Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Execution Crash

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…

Root Cause

We're on the Pro plan running a production workflow set (TroikaBot) and recently hit a status=crashed execution on a worker workflow. The workflow was an LLM chain inside map_1 (workflow id 8eTTX2r89oFF56ZV). The exec died at ~600 ms with crashed status; runData was sanitized on the exec record. We strongly suspect a transient memory/process event because re-running the exact same input 5 times back-to-back today all succeeded.

Fix Action

Fix / Workaround

We are not asking for a workaround — we have detection in place for re-occurrence. We just want a quantitative anchor for future prompt-shrinking ROI calculations and for capacity planning. Even an order-of-magnitude answer ("on Pro the cap is around X MB") is useful.

RAW_BUFFERClick to expand / collapse

Hi n8n team,

We're on the Pro plan running a production workflow set (TroikaBot) and recently hit a status=crashed execution on a worker workflow. The workflow was an LLM chain inside map_1 (workflow id 8eTTX2r89oFF56ZV). The exec died at ~600 ms with crashed status; runData was sanitized on the exec record. We strongly suspect a transient memory/process event because re-running the exact same input 5 times back-to-back today all succeeded.

Question: can you confirm the per-process memory cap for workflows on the Pro plan? Your hosted documentation page at https://docs.n8n.io/hosting/scaling/memory-errors/ does not state a number, and the admin/billing pages do not expose this either.

We are not asking for a workaround — we have detection in place for re-occurrence. We just want a quantitative anchor for future prompt-shrinking ROI calculations and for capacity planning. Even an order-of-magnitude answer ("on Pro the cap is around X MB") is useful.

Crash exec id for your reference: 304765 (workflow 8eTTX2r89oFF56ZV, started 2026-05-24T23:00:45Z).

Thanks.

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 Execution Crash