Loop Spillover between Workflows

Questions
1

Hello everyone, I was running Workflow A (Google Sheets → X → Loop) manually while building a separate, unrelated Workflow B (also Google Sheets → Y –> Loop) in a different tab. While editing Workflow B — without having executed it — the Loop node’s output panel started showing execution results that clearly originated from Workflow A. Has anyone seen this kind of cross-workflow output bleed before?
Has anyone encountered this issue as well? The outputs of the loop in the image are executions from another workflow, I have not executed this node yet.

image
image1990×856 58.5 KB

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(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.)

Share the output returned by the last node

Information on your n8n setup

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

This is a known behavior with how n8n caches output panel data in the browser’s local state. When you run a workflow, the output gets stored against the node’s ID. If two nodes across different workflows happen to share the same ID (which can occur with duplicated workflows), the panel can pick up the wrong execution data.

As @Dharmendra_Kumar suggested, checking the Loop node id in both workflow JSONs is the quickest way to confirm. If they match, the fix is simple - just delete and recreate one of the Loop nodes in the other workflow to generate a fresh ID.

If the IDs are different, it might be a browser caching issue. Try a hard refresh (Ctrl+Shift+R) or clearing the site data for the n8n domain and see if it persists.