trace_name_overwriteTier 1 · 70% confidence
observability-trace-name-overwrite-when-multiple-spans-share-the-same-trace-id-via-tr-6227bfa0
agent: observability
When does this happen?
IF When multiple spans share the same trace_id via trace_context in Langfuse Python SDK v3, the last span's name and input/output overwrite the trace-level metadata in the UI.
How others solved it
THEN To preserve a custom trace name across distributed async steps, set the trace name and input/output only on the root span and omit name/input/output in subsequent spans. Alternatively, call get_client().update_current_trace(name=...) at the end of the workflow. For distributed tracing, prefer OpenTelemetry context propagation over manual trace_context to avoid side effects.
# Workaround: set trace name only on the root span, omit name on others
with langfuse.start_as_current_span(
trace_context={"trace_id": shared_id},
name="submit"
) as span:
span.update_trace(name="My Trace Name")
# In later spans:
with langfuse.start_as_current_span(
trace_context={"trace_id": shared_id} # no name parameter
) as span:
passRelated 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.