Problem running workflow: Connect a trigger to run this node

[korovaevda]

Hello! I’ve just updated to the latest version 1.81.4.

When running a node in debug mode, an error message started appearing “Connect a trigger to run this node”.
When start first node in chain, it execute fine. Start second and get an error.
The console shows that the request rest/workflows/HbwvB9JIsU72Gdxw/run?partialExecutionVersion=2 is being executed and it ends with error 500.

This only appeared in this version, there was no such behavior before. Is this a feature or a bug?

What is the error message (if any)?

Problem running workflow
Connect a trigger to run this node

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.81.4
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Ubuntu 22.04

[hrishikesh]

Could you share your workflow?

[korovaevda]

Any two nodes connected in series.
The first one is executed correctly, the second one fails

[BramKn]

If you want to run a workflow it requires a trigger node. Click on the “Add first step” to add one. you can add a manual trigger to trigger manually.
Not sure why you would not be able to just trigger your second node though, normally this would work.

[korovaevda]

Thanks for the answer. I know that. I’ve already done dozens of workflows. But this behavior appeared only in version 1.81.0. In earlier versions, this behavior was not observed.
I just checked. In version 1.80.3 nodes are executed sequentially without triggers. In version 1.81.0 - this error appears

[BramKn]

Then it is a bug indeed. I will also try to check later to verify on my instances.

[korovaevda]

Today I installed version 1.83.0
it also has this problem
can you tell me, do I need to create a ticket somewhere so that the developers pay attention to this?
This is a very nasty bug. There are difficulties with debugging workflow

[BramKn]

Does seem to work here I just installed 1.83.2 and tested.

Sorry for the late reply.

[korovaevda]

just installed version 1.83.2.
If you run the second node at once. It runs the first and second without errors.
If you run the first one sequentially, it runs successfully, run the second one, an error appears here
Watch this screencast https://youtu.be/6C6R_UMerZM
https://youtu.be/6C6R_UMerZM

[zakiki]

I’m having the same issue trying to trigger a Basic LLM node - i havent had the issue with any other node till today

[ncsaf]

I was having the same problem until now. But seeing your screencast, I realized that I don’t need to press the trigger first and then the last node. Now only on the last node it already executes my project.

[Sebas]

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

if you think this is the answer please hit the ‘solution’ button