tracing with Langsmith split a run in multiple traces

[snova-jorgep]

Bug Description

when tracing with arize, each run creates as many traces as llm based components are in the flow

Reproduction

use a template with more than one llm or agent component, execute one run, in arize it will appear several independent traces that can't be join together or attached to an specific run by any key

Expected behavior

complete flow run under only one trace

Who can help?

No response

Operating System

mac os sequoia 15.1

Langflow Version

1.2.0

Python Version

3.10

Screenshot

in the image both independent traces are two agent from the same flow

Flow File

No response

[dosubot]

I found a similar open issue regarding the problem of tracing with Langsmith splitting a run into multiple traces when using multiple LLM or agent components in Langflow. The suggested solution involves ensuring that the trace name and run ID are consistently set across all components in your flow. This might require checking the initialization and management of tracers in the TracingService to ensure they are correctly linking all components' traces to a single run. If this behavior is not configurable in the current version, it might require a change in how Langflow handles trace grouping for complex flows with multiple components ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}