I am having an issue with workflow that previously worked but I have not used it for a while so I do not have the exact version that it got broken. I have a workflow that processes a csv file that is sent through Telegram.
What is the error message (if any)?
Error reads Cannot read properties of undefined (reading 'disabled')
Stack trace
TypeError: Cannot read properties of undefined (reading 'disabled') at WorkflowExecute.checkReadyForExecution (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:557:22) at WorkflowExecute.processRunExecutionData (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:708:37) at startExecution (/usr/local/lib/node_modules/n8n/dist/workflow-execute-additional-data.js:173:43) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.executeWorkflow (/usr/local/lib/node_modules/n8n/dist/workflow-execute-additional-data.js:138:12) at ExecuteContext.executeWorkflow (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/base-execute-context.js:58:24) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/ExecuteWorkflow/ExecuteWorkflow/ExecuteWorkflow.node.js:336:41) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:633:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:882:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1216:20
I tried updating the Execute workflow node from 1.1 to the latest 1.2 but I am getting still the same error.
Please share your workflow
The target workflow has a failed execution but even the âExecute Workflow Triggerâ does not have any data.
So I actually did find something out! I wanted to process the csv manually, without my TG bot, but it was failing with the same error when I tried to âTest workflowâ.
I noticed that the Sum node was behaving somewhat odd. The csv file has a âBooking ref.â column that it did not really like (the dots again âŚ). But I worked around that and counted a different column initially. But when I updated that node from 1 to 1.1, I can suddenly âTest Workflowâ.
I created a new workflow and started anonymizing it to share it, but that one works even with the old Sum node. I am confused now⌠I mean my workflow is working so I am happy, but I have nothing to proof that there was an error in the first place. Should I consider it âfixedâ?
I am experiencing it again. When my workflow with a file fails, I then fix it and when I want to rerun it, it fails with the error âCannot read properties of undefined (reading âdisabledâ)â. Sending the file again is the only option.
Attaching stack trace as I missed that last time
TypeError: Cannot read properties of undefined (reading 'disabled') at WorkflowExecute.checkReadyForExecution (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:584:22) at WorkflowExecute.processRunExecutionData (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:737:37) at startExecution (/usr/local/lib/node_modules/n8n/dist/workflow-execute-additional-data.js:172:43) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.executeWorkflow (/usr/local/lib/node_modules/n8n/dist/workflow-execute-additional-data.js:137:12) at ExecuteContext.executeWorkflow (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/base-execute-context.js:58:24) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/ExecuteWorkflow/ExecuteWorkflow/ExecuteWorkflow.node.js:349:41) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:660:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:891:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1224:20
I am now on 1.81.4 self hosted.
Edit: I see that I actually attached the stack trace previously. n8n container log also just says the main error.
I noticed that when I click on âDebug in Editorâ button it takes the failed execution into the editor - no surprises here. Everything is there, from the input data all the way to the failed node. But when I hit âTest workflowâ it fails as expected but also the input Binary data are gone from the pinned first node. Can that be it?
EDIT: The issue is not in the binary. I converted the binary to base64 at the very beginning and the third workflow still does not start.
Well after a lot of testing a made it working. The workflow was not running at all. I tried duplication and copy paste but nothing. Then I started deleting nodes and there I found that n8n did not like the Extract from File node being the second node in the workflow. So I tried thisâŚ
it worked for me man!!!
can not believe it , I just deleted some parts of my workflow and after that I saw that error and with your trick it works again
For future reference â this happens occasionally when duplicating a workflow. Seems to be some type of weird corruption. As others have pointed out, duplicating the nodes and/or duplicating the workflow again can sometimes help.
âŚ). But I worked around that and counted a different column initially. But when I updated that node from 1 to 1.1, I can suddenly âTest Workflowâ.