"Cannot read properties of undefined" in no operation node #13086
Comments
|
Hey @Fank, We have created an internal ticket to look into this which we will be tracking as "GHC-748" |
Joffcom
added
the
in linear
|
using the error execution in editor and then rerun the noop node I get exactly:
As you can see I have values from the Filter node before, so it should just forward them. |
|
Removing the noop node works perfectly fine:
But even having a connected but disabled noop node, still causes issues:
|
|
That is really odd the noop node doesn't do anything it just passes on the input. Are you able to share the json output of the jira trigger and the redis node so we can pin it and see if we can reproduce this? |
|
@Joffcom Sure but since the jira trigger will may contain sensitive information, is there any way I could send them to you without posting them public? |
|
The error seems to be coming from this line, which could only happen if somewhere in the code something was messing up If you can switch to this custom image, we can confirm this theory. Also, when the error happens, can you check the server logs to look for a line containing "node missing in". That might also shed more light on the issue. |
|
Thanks for providing a debug image, I will update the image once we reached low traffic and post new findings. |
|
@netroy I updated the image and reimported the same json I attached above (because I modified the workflow to make it work again). After execution I got the same error again, but this time with Information you added: 
IIRC |
|
I just checked each workflow node again, I can't find any reference to |
|
That just look weird. Can you deactivate the workflow, and reactivate it again, and then check if the issue persists? |
|
I disabled it, waited a minute and enabled it again:
|
|
Can you please also try duplicating this workflow, deactivating the old workflow, and then activating the new workflow? |
|
also, would it be possible to for you to share your database with us over support channels? If that's possible, please contact [email protected], with your sqlite file, and a link to this ticket, and we'll try to get this addressed as soon as possible 🙏🏽 |
|
@netroy email has been sent, with all needed Information. |
|
Not sure, but maybe it could be related to #12159 , the code you changed and the error shown in this issue looks like the behaviour I have. |
|
Yes, the underlying cause looks to be the same between these two issues. But it's still not clear why the execution engine is using node names that don't exist anymore. we are still investigating. |
|
We still haven't managed to narrow this down, or reproduce this. |
|
@Fank Can you download the workflow in question as JSON, open it an editor, and check that the |
|
@netroy could you give me a hint of how to access this information? |
Joffcom
added
In Review
|
if you open the workflow in your browser, you can use use the menu on the top-right corner to download the workflow as a JSON file
Once this file is downloaded, you can open it in a text editor locally, to check if the node in questions is defined just in |
Joffcom
added
Needs Feedback
|
Had the exact same error ( A node in "Merge": {
"main": [
[
{ "node": "Merge2", "type": "main", "index": 0 },
{ "node": "Loop Over Items", "type": "main", "index": 0 }
]
]
}Steps to reproduce:
Fix:
Let me know if you need more details! I don't want to share my full |
Joffcom
added
In Review
|
Thanks for confirming this. I suspect this issue is caused by some recent frontend changes. We'll try to get it fixed in the next day or two. |
Joffcom
added
Needs Feedback
|
We'll release this fix in a patch release tomorrow morning. |
|
@netroy issue is still present in latest patch. |
|
@a-salim-main we'd need more information than that. What nodes are you seeing these errors with? is there a stacktrace that you can share with us? maybe share a screenshot of the error that you see on the frontend. |
|
@netroy I encountered it with 1.81.4 as well again, this time when migrating our workflows from CE to EE 1.79.3 -> 1.81.4, by downloading JSON and importing it again.
After removing the code node, everything was fine. |
|
can you please download the workflow json, open it in an editor, and check if there are any connections for nodes that are not in the workflow? |
|
@netroy the switch node: "connections": {
"Switch": {
"main": [
[
{
"node": "Merge1",
"type": "main",
"index": 0
},
{
"node": "add billable time",
"type": "main",
"index": 0
}
],
[
{
"node": "Merge1",
"type": "main",
"index": 0
},
{
"node": "add billable time",
"type": "main",
"index": 0
}
],
[
{
"node": "Import worklog delete",
"type": "main",
"index": 0
}
]
]
}, |
|
We're able to reproduce this now reliably, and are working on a fix. |
Bug Description
When calling a workflow i see items in between each node, but then suddenly it stops and i get following error:
The filter node before the noop node has no undefined fields in its conditions:
To Reproduce
Maybe hard to explain or reproduce, it is basically everytime it follows this path:
Using attached workflow:
Post_discord_notification_on_scope_change.json
Expected behavior
Continue executing the workflow like it is designed to be.
Operating System
Ubuntu 20.04.6 LTS
n8n Version
1.76.3
Node.js Version
docker
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: