Hi everyone,
I am running into a recurring issue with a production workflow where executions are marked as Crashed, but no error details are available, making it very difficult to debug.
Environment
-
n8n version: v2.1.4
-
This behavior started after upgrading from v1.x.x to v2.1.4
-
Trigger: Schedule Trigger
What happens
-
The workflow runs successfully for several loops, then suddenly stops
-
Executions appear as Crashed in the Executions panel
-
When opening the execution, I see:
“Can’t show data. The execution was interrupted, so the data was not saved.”
-
No node shows an error
-
The configured Error Workflow is not triggered
-
After multiple crashes, n8n automatically deactivates the workflow with:
“This workflow was automatically deactivated due to multiple crashed executions”
-
I then have to manually reactivate it
Workflow context
-
The workflow loops over items and performs:
-
External scraping
-
Data merging
-
Filtering and object creation
-
-
Several nodes are configured with
continueRegularOutput -
Even when disabling this during testing, the behavior persists
-
This appears to be an execution interruption rather than a normal node failure
Why this is confusing
Since the execution is interrupted:
-
No execution data is saved
-
No error message is visible
-
Error workflow does not run
-
There is no indication which node caused the crash
Questions
-
What typically causes executions to be marked as “Crashed” with no saved data?
-
Can this be caused by memory limits, execution time limits, or worker restarts?
-
Is there a way to get more diagnostic information for crashed executions?
-
Is the auto-deactivation always triggered by repeated crashes, even if they are infrastructure-level issues?
-
Can automatic workflow deactivation be disabled or configured?
This behavior only started after upgrading from v1.x.x to v2.1.4.