n8n - 💡(How to fix) Fix workflow crashed after 32 seconds with all nodes showing success ID: #18378 [2 comments, 2 participants]

Describe the problem/error/question What is the error message (if any)? No specific node error. Execution log shows: "Crashed in 32.197s". Banner message: "This workflow was automatically deactivated due to multiple crashed executions."

TL;DR

The workflow crashes intermittently after 30-45 seconds with a "Crashed" status, despite individual nodes showing "Success" in the execution logs, suggesting a potential issue with the workflow's overall execution or timeout settings.

Guidance

• Review the workflow's configuration and nodes to ensure there are no hidden errors or timeouts that could be causing the crash, even if individual nodes are reporting success.
• Check the execution logs for any patterns or clues that might indicate what's happening in the last 30-45 seconds before the crash, as the provided log only shows a "Crashed in 32.197s" message.
• Investigate the n8n settings for automatic deactivation due to multiple crashed executions to understand if there's a threshold or setting that can be adjusted to prevent premature deactivation.
• Consider adding more detailed logging or debugging statements to the workflow to capture more information about what's happening during execution, especially right before the crash.

Notes

The issue seems to be related to the workflow's execution or the n8n platform's handling of it, rather than a specific node error. Without more detailed logs or information about the workflow's configuration and the nodes involved, it's challenging to provide a more specific solution.

Recommendation

Apply workaround: Adjust the workflow's configuration or n8n settings to prevent automatic deactivation and add more logging to capture detailed information about the crash, allowing for a more targeted investigation.