App Router: OTel spans during cache component fallback resume reuse the trace id
#1 495 ouverte le 22 mai 2026
Métriques du dépôt
- Stars
- (8 563 étoiles)
- Métriques de merge PR
- (Merge moyen 1j 1h) (462 PRs mergées en 30 j)
Description
This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext
mainvs Next.jsv16.2.6, 2026-05-22).
Problem
Spans created during fallback resume inside a Cache Component should have a fresh trace id distinct from the build-time render. vinext reuses the same trace id (e.g. 11989306), implying the span context is not being re-created per request resume.
Trace id reused across build-time render and runtime resume
Estimated Impact
~1 test failures across the deploy suite.
Affected Test Suites
test/e2e/app-dir/cache-components-allow-otel-spans/cache-components-allow-otel-spans.test.ts
Recommendation
-
Reproduce first in vinext's own test suite. Use the existing
cache-components-allow-otel-spansfixture and assert the trace id changes between build-time prerender and runtime resume. -
Reset the OTel context on resume. Each cache-component resume should start a new span/trace context, not inherit the prerender's.