Describe the problem/error/question For some reason, nodes that are pinned in my workflow are showing as “Pinned” in the execution tab even though the execution is not a test execution. [image] I have tried unpinning the node, however it still shows as “Pinned” in executions after the node has be…

Hi @Evan711 It appears your n8n interface is showing a “Pinned” badge by mistake, which is likely a visual error rather than a problem with your actual workflow data. Even though you have unpinned the node, your browser or the n8n cloud service might be “remembering” the old setting due to a cachin…

@Evan711 the orange/yellow icon on “When Executed by Another Workflow” might not actually be the pinned-data indicator — it can also be n8n’s visual cue that the trigger received input data from a parent workflow’s Execute Workflow node. is the actual pinned content still showing up in the input/out…

Welcome @Evan711 to our community! I’m Jay and I am a n8n verified creator. Achamm’s instinct is right - the orange indicator on the “When Executed by Another Workflow” trigger node does not mean pinData is active. It’s n8n’s visual cue that the trigger received live data from a parent workflow’s E…

Posting here instead of opening a new issue because I’m pretty sure I’m seeing the same thing. I had an issue this morning where a webhook was triggered three times. When I look at the webhook node in n8n, it not only shows that the data is pinned, but it shows the pinned data on the output instead …

Thanks Adrian! Your video demonstrates exactly the issue im running into. Glad to know I’m not crazy. Definitely an issue with n8n and not my browser.

I am facing the exact same issue and it is causing critical errors in our workflows. Just like you mentioned, pinned nodes are now bleeding into production executions. This completely defeats the purpose of the feature, as we rely on pinned data solely to test flows in the editor without affecting …

I’m not seeing pinned data go into production execution. Only that the execution panel shows pinned data instead of the actual trigger data. If you have proof that your production workflows are running with pinned data, I would encourage you to make a video of that and attach it to the issue that I …

My issues was closed as a duplicate of an earlier issue which they say was a regression (fancy way of saying, “an unintentional bug that was introduced by a new feature and broke something that was already working,”) and will now be fixed in 2.22.6. They apologized for the inconvenience.

@adriandotgoins @Thiago_Domingues @Evan711 bem vindos à comunidade n8n. nova release em 01/06 com acertos. Release notes | n8n Docs

@adriandotgoins You are absolutely right. After doing some deeper testing based on your reply, I realized that the issue is indeed visual, just as you described. The real incoming data is actually being processed correctly under the hood. However, the major aggravating factor here is that the exec…

Bug: Los nodos aparecen como "Fijados" en ejecuciones de workflow sin pruebas

Preguntas

Chrevor 2 Junio, 2026 15:07 14

Gracias por tu minuciosidad. El contenido generado por IA está haciendo esto desagradable

Hice otro post aquí: Pinned Node in execution view is annoying

Tema		Respuestas	Vistas
Pinned Data should not show in Executions Feature Requests	5	600	18 Enero 2023
Data Pinning doesn't work (again?) Questions	4	854	23 Marzo 2025
Test Step does not work, but execute workflow does Questions	9	1510	4 Noviembre 2024
Bug: Pinned data on this node is corrupted and can't be displayed Questions core , workflow-building	6	158	28 Mayo 2026
Pinned data is shown even on past production workflow executions Questions data-pinning	3	749	18 Enero 2023

Bug: Los nodos aparecen como "Fijados" en ejecuciones de workflow sin pruebas

Temas relacionados