I manually started the workflow. In Executions I can see that it is running. At least 20 minutes. Then failed and executions detail shows it failed after 0.03s
And I don’t see any node on which the workflow failed.
Error message send by error workflow says
Error workflow - 18 - Transfer Xenie to DB - feedback
Last node executed ERROR - Execute Workflow - Transfer feedaudit
Mode - integrated
Error Message - Workflow has been canceled or timed out!
Stack - WorkflowOperationError: Workflow has been canceled or timed out!
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1031:84
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1062:20
Please share your workflow
Information on your n8n setup
n8n version: 1.37.3
Running n8n via (Docker,:
Anybody got any advice?
I need to find out exactly what it’s failing on.
Thank you
Hello @Petr_Mindl , I’ve also encountered this issue repeatedly. Even though in the back, the workflow’s done executing, the UI says otherwise. What I usually do is refresh the page when I’m pretty sure that the workflow should be done executing by now. I know it’s a bit messy, but it’s a simple fix that works most of the time.
Actually, I described it wrong. The workflow will end with an error even if it is run via a time trigger or another workflow. But according to the “work done” (even by running the following workflow), it seems that the workflow was done correctly.
does anyone know?
When the workflow is run by another workflow or by cron, in Executions it is Failed and time Failed in 0.01s. But it definitely ran longer.
At the same time if I look at the specific Executions, it doesn’t show any error.