n8n - 💡(How to fix) Fix Can't copy to editor previous executions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28621Fetched 2026-04-18 05:57:05
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

When trying to reproduce a previously executed execution from the list, after clicking on it, and confirming "Unpin" on the message box that appears, data from the trigger node doesn't actually update if previous data from another execution was already pinned. Visually, it appears that new data is there, but when executing on test mode, all the execution goes through using the previously stored data.

What is the error message (if any)?

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.16.1
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

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

pruning

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

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-17T13:24:39.601Z

extent analysis

TL;DR

The issue can be resolved by properly handling pinned data from previous executions, potentially by updating the workflow to clear or update pinned data when a new execution is selected.

Guidance

  • Verify that the "Unpin" action is correctly implemented and actually removes the pinned data from the trigger node.
  • Check the workflow configuration to ensure that it is set up to update the data from the trigger node when a new execution is selected.
  • Investigate if there are any caching mechanisms in place that might be causing the old data to be retained.
  • Test the workflow in a controlled environment to isolate the issue and identify the root cause.

Example

No code snippet can be provided without more information about the specific workflow and nodes being used.

Notes

The issue seems to be related to the handling of pinned data in the workflow, but more information about the specific workflow and nodes being used would be necessary to provide a more detailed solution.

Recommendation

Apply a workaround by manually clearing the pinned data from the trigger node when a new execution is selected, until a more permanent solution can be implemented. This is because the current behavior is causing unexpected results and a workaround can help mitigate the issue until a proper fix can be found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Can't copy to editor previous executions [1 comments, 2 participants]