Execute node - Pinned data

“Execute node” with input pinned data, always execute all previous nodes instead of “watching” only what already received.

What is the error message (if any)?

Please share your workflow


Share the output returned by the last node

No output because he is expecting the start node instead of using what he have already in “INPUT”

Information on your n8n setup

  • **n8n version:0.222.0
  • Running n8n via (Docker):

Hi @cenasdanet, welcome to the community!

I believe this is expected - you’d need to pin data on all nodes you don’t want to execute (or alternatively disable these nodes temporarily).

Hi @MutedJam, thank you for the answer.
For debug purpose is not that “user friendly”.
But thanks anyway.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Hi @cenasdanet, Max from n8n’s design team here. Just wanted to let you know that I’m assessing whether this functionality should be changed to only execute up to the pinned node (but not before).

Since posting your request…

  • How often has this come up/ been an issue for you?
  • What would you expect to happen in a scenario where a node references data from earlier in your flow (i.e. before pinned node) and that node has not yet executed?


1 Like