n8n 2.43.8 Disables Expression Traces by Default, Keeping Workflow and Node Spans

A patch changes expression-level tracing defaults

n8n released stable 2.43.8 on October 19, 2026, changing the default so expression.evaluate trace spans are not created unless explicitly enabled. Self-hosted teams using OpenTelemetry should review configuration and received telemetry after upgrading. Expressions in workflows are not being disabled.

OpenTelemetry records and exports operational telemetry; a span is a timed unit of work. With tracing configured, n8n sends spans to the operator’s OTLP endpoint. Expression-level spans are more granular than workflow or node spans.

The upstream change has a narrow scope

Upstream PR 41211 and backport 41310 change the expression-tracing variable from a default of true to false; the exact environment-variable name is provided in the linked source PR. Explicit true remains available. Workflow, node and agent spans and expression metrics are unchanged; the observability variable retains its true default.

Maintainers explain that internal expression-engine spans should not go to customer endpoints by default and report an endpoint flooded with them. That is an upstream account, not Friday Works measurement or evidence of data theft, a CVE or active attack.

Friday Works recommends checking whether OpenTelemetry is enabled and the variable is explicitly set. A configured true value should not be assumed to disappear when the software default changes; inspect effective configuration after restart.

Keep stable and pre-release tracks separate

The release lists 2.43.8 as stable and 2.44.4 as a pre-release on the same date. The latter also changes webhook log-stream connection reuse. Do not attribute every pre-release fix to stable 2.43.8.

Friday Works recommends a specific version tag, existing backup procedures and a suitable test environment before an authorized production update. This report does not upgrade customer systems.

Fewer spans do not prove faster workflows or a quantified cost reduction. Check whether missing expression spans are expected or the collector stopped receiving all traces; those outcomes require different responses.

Validate with an owned sample workflow and collector

Upstream’s test calls for a workflow using expressions with OpenTelemetry enabled: the collector should receive workflow and node spans without expression.evaluate spans under the new default. Explicitly enabling the variable can restore slow or failed evaluation spans; not every evaluation is promised a span.

Friday Works suggests a non-sensitive sample workflow and before/after checks of business output and telemetry. A string transformation should still produce its expected value; reduced telemetry is not a reason to skip logic validation.

The image is n8n’s genuine archival Expression Editor demonstration. It is not a collector, a new 2.43.8-specific interface or evidence that Friday Works tested this release. The source and Apache 2.0 with Commons Clause notices are retained.