n8n - 💡(How to fix) Fix Workflow crashes without any information or logs [1 comments, 2 participants]

Describe the problem/error/question

I have a workflow that kicks off every morning and processes some data with AI. For 3 days is a row it now crashes. When I open it, there is no information about where it crashed. Logs are also empty. No specific error message either.

What is the error message (if any)?

No, just "Error"

• error: all

TL;DR

Check the workflow's node configuration and execution history to identify the point of failure, as the empty logs and lack of error messages suggest a potential issue with the workflow's design or a node's behavior.

Guidance

• Review the workflow's nodes and their connections to ensure that they are properly configured and that there are no circular dependencies or missing connections.
• Check the execution history of the workflow to see if there are any patterns or commonalities between the failed executions, such as a specific node or set of nodes that are consistently failing.
• Consider enabling the "progress" storage option to capture more detailed information about the workflow's execution, which may help identify the point of failure.
• Verify that the AI processing node is properly configured and that the input data is valid and consistent.

Example

No code snippet is provided as the issue does not contain sufficient information about the specific nodes or code used in the workflow.

Notes

The lack of error messages and empty logs suggests that the issue may be related to the workflow's design or a node's behavior, rather than a technical issue with the n8n platform. The fact that the workflow crashes without providing any information about the point of failure makes it difficult to provide a more specific solution.

Recommendation

Apply workaround: Enable the "progress" storage option and review the workflow's node configuration and execution history to identify the point of failure, as this may provide more detailed information about the issue and help resolve it.