Tracing now captures workflow version IDs
Workflow executions are now traced with their version ID, making it easier to debug issues and track behavior across workflow updates.
n8n workflow executions now carry version information through OpenTelemetry traces. When a workflow starts, the trace captures not just the workflow ID and name, but also the specific version that ran. This matters for debugging — when something goes wrong, engineers can now trace back to exactly which version of a workflow was responsible, without manually correlating timestamps across separate systems. The change sits in the tracing module and surfaces the version ID as a structured attribute that observability tools can query and filter by. It forms part of a broader effort to improve observability across the platform.
View Original GitHub Description
Summary
Add workflow version id to otel tracing
<!-- Describe what the PR does and how to test. Photos and videos are recommended. -->Related Linear tickets, Github issues, and Community forum posts
closes ligo-456
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/[TICKET-ID] --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)