Form Node shouldnt "pin"

Questions
1

Describe the problem/error/question

When using the Form node and debugging, you often end up with pinned data. This breaks subsequent “execute workflows” in every situation i can think of, since the form doesnt come up and you cant click on anything. Im not sure why youd want to do this. Its confusing and Im always fighting with it.

What is the error message (if any)?

None

Information on your n8n setup

Cloud, latest

2

Always unpin the form node after testing

After testing the Form node:

  • Click the node → check if there’s a :pushpin: pin icon lit up.
  • If yes, click it to unpin the data.
  • This lets the form show up again on the next run (instead of reusing old data).

or you can use a dedicated testing workflow

To avoid messing with the real one:

  • Create a small, separate workflow that just runs the Form node.
  • Test there, unpin, and then plug it into your main workflow.
3

Hi there,

Can you give an example with screenshot(s) where it is causing issues?
Pinning data is always a manual action, unless they changed that in a new version.
So you can simply decide not to pin the data.
Also pinning data is one of the best features for debugging. For example, you do not need to fill in the form over and over again while developing.
So I am very curious what is causing issues with it for you.

4

Here is one of many flows that “pins data automatically”.

  1. from main workflow call a sub. Have the sub “stop and error” simulating a normal bug.
  2. run the main. when it errors click “debug in editor” to debug the sub.
  3. now fix the error and hit save.

You have just inadvertently “saved” that the data is pinned for all views/instances of the Sub. To test this open a new window to that sub and note that the data is pinned. You might come back days later to debug the sub, and not realize its pinned, and that is very hard to notice why its not working as intended.

There are 2-3 other ways i stumble into this trap also, ill note them when i realize what they are.

@Abrar_Sami
@BramKn