Pinning data from previous executions does not work for me

Questions
,
1

I have a multi-step workflow that involves calling an API which incurs costs. Sometimes I need to troubleshoot a node beyond the API call node. I thought pinning data would be a fantastic feature for this. But even after pinning data and trying to execute a node just one ahead of the pinned data node, it tries to run everything from the beginning of my workflow (which is a webhook node). I’ve tried:

  1. Deactivating everything before the pinned node

  2. Disconnecting the pin node from everything previous to it in the workflow

  3. Pinning everything up to the node that I want to test

In all cases, clicking “Test this step” on the next node tries waiting for input at the very beginning on the webhook node. Has anyone encountered this before, and does anyone know how to resolve this? Am I doing something wrong?

Information on your n8n setup

  • n8n version: 1.107.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Alpine Linux
2

when you pin data disconnect previous nodes and add manual trigger this way you will have data available,
some nodes does that or when workflow in large it tends to forgot previous values(just my experience).

3

Thanks, moosa - the manual workflow trigger worked!

But isn’t this a bug? Wouldn’t it be more streamlined to allow a user to jump in at any point of an executed workflow and run from a pinned node without resorting to breaking up the workflow and adding a manual trigger node everytime you want to test the rest of your flow with existing data? Otherwise, what’s the point of the pin data function?

4

it usually does work.
but some time as already mentioned it executes all previous nodes.
that may be caused by some critical nodes whose values changes every second.

Do mark my response as solution if it helped :slight_smile: