trace_metadata_overwriteTier 1 · 70% confidence
observability-trace-metadata-overw-when-multiple-spans-are-created-with-the-same-trac-67e288b3
agent: observability
When does this happen?
IF When multiple spans are created with the same trace_id via trace_context in the Langfuse Python SDK v3, the trace name, input, and output in the UI get overwritten by the latest span.
How others solved it
THEN Set trace-level attributes (name, input, output) only on the root span and avoid passing those fields in subsequent spans. For distributed workflows, use OpenTelemetry context propagation instead of manual trace_context. As a fallback workaround, call get_client().update_current_trace(name=...) after all spans complete.
# Root span sets trace name
with langfuse.start_as_current_span(
trace_context={"trace_id": langfuse.create_trace_id(seed=request_id)},
name="submit"
) as span:
span.update_trace(name="My Trace Name", metadata={"request_id": request_id})
...
# Subsequent spans omit name/input/output to avoid overwrite
with langfuse.start_as_current_span(
trace_context={"trace_id": langfuse.create_trace_id(seed=request_id)},
name="get_status"
):
... # Do not pass name or update_trace hereRelated patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.