Connect a trigger to run this node” Error on Sequential Node Execution in v1.83.2

[Najmul_haq_Southun_n]

Hello everyone,

I’m experiencing an issue with n8n version 1.83.2 on my self-hosted Docker setup. When I run a workflow that starts with a valid trigger node, the first node executes without problems. However, if I attempt to execute the subsequent node separately (or sequentially after the first node), I receive the error “Connect a trigger to run this node.”

This behavior wasn’t present in earlier versions (like v1.80.3), where nodes executed in sequence without error. I’ve double-checked my workflow connections, and the trigger is properly set up at the beginning.

Has anyone encountered this issue with sequential node execution (especially with nodes like the Basic LLM node)? Is there a workaround or a fix in progress for this version? I’d appreciate any suggestions or troubleshooting tips.

Thank you in advance!
Najmul Haq

[Sebas]

So it seems to be a bug, this has been reported by more users. Up towards version 1.82.3. I have not upgraded yet I am still on 1.81.4 and confirm the issues is not present in this version

if this anwers your question the please hit the ‘solution’ button

[Sebas]

This is confirmed by n8n to be a bug, the engineers of n8n will be working on this next week.

if this anwers your question the please hit the ‘solution’ button