n8n - 💡(How to fix) Fix Execution view shows pinned data instead of actual runtime data [1 comments, 2 participants]

Bug Description

When a node has pinned data configured for development purposes, the execution view of a published workflow may show the pinned data instead of the actual runtime input.

The workflow itself appears to execute correctly using the real incoming data, but the execution details shown in the UI still display the pinned values.

To Reproduce

• Create and publish a workflow containing a Webhook node with pinned sample data. For example, a simple GET webhook expecting a "name" query parameter can have pinned data such as name=foo.

• Once the workflow is published, trigger the webhook with a different value, for example name=bar. Then, open the corresponding execution in the "Executions" tab and inspect the input data of the Webhook node.

• The execution view shows the pinned data (name=foo) instead of the actual runtime data (name=bar). Even though the workflow appears to execute correctly with the real request, the execution history shown in the UI still reflects the pinned values.

Expected behavior

The execution details should display the actual runtime input received by the webhook, regardless of whether pinned data is configured on the node for development purposes.

For example, if the webhook is triggered with name=bar, the execution view for the Webhook node should show name=bar, not the pinned sample value name=foo.

Debug Info

core

• n8nVersion: 2.21.4
• platform: docker (cloud)
• nodeJsVersion: 24.15.0
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 50
• license: enterprise (sandbox)
• consumerId: 00000000-0000-0000-0000-000000000000

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions