Execution always starts from the beginning

Questions
1

Hi all,

I’m on n8n version 1.108.0 (cloud), and I’m running into an annoying issue with the “Execute Node” feature:

Whenever I try to execute a single node (e.g., a Code node), the workflow always starts from the beginning, even if I’ve already run the workflow once from the start, and I haven’t edited any previous nodes.

Things I’ve checked:

  • I use Manual Trigger for development/testing.

  • I run the workflow from the start first, so upstream nodes should have data.

  • I haven’t made any changes to upstream nodes when trying to execute just one node.

  • Cached data appears visible in the UI for upstream nodes.

  • My workflow is pretty linear (no complex merging/branching).

  • I’ve tried in multiple browsers and cleared cache, and the issue persists after updating to the latest n8n version.

Is this expected behavior, a bug, or am I missing something basic?
Are there any workarounds to efficiently test single nodes without re-running the whole workflow every time?

Thanks for any help or tips!

2

Hi there, you can try to pin the data of the previous nodes, this will make sure it will not get triggered and the data will persist for the node that you pin

You can read more about it here

4 Likes
3

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