In the executions log, n8n is seen to sometimes call a workflow that was published a long time ago (even though this workflow has long been updated). #26075
Description
Describe the problem/error/question
In the executions log, n8n is seen to sometimes call a workflow that was published a long time ago (even though this workflow has long been updated).
Currently encountering some strange issues (similar to caching), hoping to receive your advise, thank you.
What is the error message (if any)?
Please share your workflow/screenshots/recording
The latest workflow is as follows:
Execution the workflow and check the executions log. (This is a workflow published a long time ago, the same as the one in the first screenshot. )
But, this issue does not always occur. There is still a chance that it will call the current latest workflow, as follows:
(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
Debug info
core
- n8nVersion: 2.7.2
- platform: docker (self-hosted)
- nodeJsVersion: 22.22.0
- nodeEnv: production
- database: postgres
- executionMode: scaling (multi-main)
- concurrency: -1
- license: enterprise (production)
storage
- success: all
- error: all
- progress: false
- manual: true
- binaryMode: s3
pruning
- enabled: true
- maxAge: 2000 hours
- maxCount: 60000 executions
client
- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/145.0.0.0 safari/537.36
- isTouchDevice: false
security
- secureCookie: false
Generated at: 2026-02-21T11:42:36.553Z}