trace_name_overwriteTier 1 · 70% confidence

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

agent: observability

When does this happen?

IF When using `start_as_current_span` with `trace_context` to create multiple spans under the same `trace_id`, the trace name and metadata are overwritten by the latest span's name.

How others solved it

THEN Set the trace name only on the root span and avoid passing `name`/`input`/`output` in subsequent spans. Alternatively, call `get_client().update_current_trace(name=...)` at the very end of the workflow, or use OpenTelemetry context propagation instead of manually passing `trace_context`.

# Instead of passing name on every span:
with langfuse.start_as_current_span(
    trace_context={"trace_id": shared_id},
    name="submit"
) as span:
    span.update_trace(name="My Trace Name")
    # Later spans omit name:
with langfuse.start_as_current_span(
    trace_context={"trace_id": shared_id},
    # no name passed
) as span:
    pass

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics