n8n - 💡(How to fix) Fix See executions crashing and returning 503 [1 comments, 2 participants]

Describe the problem/error/question

When I click to view the executions of a specific flow, the application gives a connection loss and a 503 error. This happens only and exclusively in one flow. its a heavy workflow with many itens that can impact the results.

What is the error message (if any)?

• error: all

TL;DR

The 503 error when viewing a specific heavy workflow's executions may be related to the workflow's size and complexity, and adjusting the pruning settings or increasing the concurrency limit might help.

Guidance

• Review the pruning settings to ensure that the maxAge and maxCount values are not too low, causing the workflow executions to be deleted too quickly.
• Consider increasing the concurrency limit to allow more executions to run simultaneously, which might help with handling the heavy workflow.
• Check the workflow's configuration to see if there are any nodes or actions that can be optimized to reduce the load on the system.
• Verify that the issue is specific to this one workflow by testing other workflows with similar complexity and size.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue might be related to the specific workflow's size and complexity, and adjusting the pruning settings or increasing the concurrency limit might only be a temporary workaround. Further investigation into the workflow's configuration and optimization might be necessary.

Recommendation

Apply workaround: Adjust the pruning settings and increase the concurrency limit to see if it resolves the issue, as this is a non-invasive change that can be easily reverted if it does not work.