Node executions always start from the start

Hello guys so after i updated my n8n it started behaving differently. Before when i add another node after executing it, i can press execute node and then the node will execute but now after the update whenever i execute a node to test it, it will always start executing from the trigger until it reach the node that i executed. It’s not like this before, I can execute it at the very last node and it will execute only on that 1 node. But now whenever i press execute this step, it will execute from the start, from the trigger. Is it just me or there’s a new setting after the update?

Yea, is something normal in newer versions.

Is when you click Execute node / Execute step now, n8n will start from a trigger (Manual Trigger, Webhook, etc.) and run through the chain up to that node, instead of only re‑running the single node using cached data.

If you want only to test one node you need to attach a Manual Trigger with some pinned data to the respective node.

So yes, is normal.

Cheers!

1 Like

So it’s a hassle now to run a node after adding it. You need to add a manual trigger everytime. It’s better before, it will only run the node that you pressed instead of starting from the trigger.

1 Like