n8n - 💡(How to fix) Fix Workflow execution status stays as 'running' after node timeout — no automatic error state transition [1 participants]

When a workflow node times out (e.g. an HTTP Request node with a long timeout or a custom code node stuck in an infinite loop), the workflow execution status in the UI remains stuck as "running" indefinitely. It never transitions to an error or failed state automatically, which makes it impossible to detect stuck workflows without manually checking each execution. After node timeout, the workflow execution status should automatically transition to "error" or "failed" state, and the execution entry should reflect the failure with a proper error message and timestamp.

TL;DR

The workflow execution status remains stuck as "running" when a node times out, and a potential fix involves modifying the workflow or node configuration to handle timeouts properly.

Guidance

• Review the workflow and node configurations to ensure that timeouts are properly handled, and consider setting a reasonable timeout value for each node.
• Investigate the n8n documentation for any built-in features or settings that can help detect and handle stuck workflows, such as automatic retry mechanisms or timeout settings.
• Consider implementing a custom solution, such as a separate monitoring process or a script, to detect and update the status of stuck workflows.
• Check the n8n version and Node.js version for any known issues or updates that may address this problem.

Example

No specific code example is provided, as the issue seems to be related to the workflow configuration and node settings.

Notes

The issue may be specific to the self-hosted deployment and the SQLite database. Further investigation is needed to determine the root cause and the most effective solution.

Recommendation

Apply a workaround, such as implementing a custom monitoring process or modifying the workflow configuration, as the issue may be related to the specific deployment and configuration.