Lyzr Proxy creates multiple traces for one agent run

[utshomax]

When lyzr model ( custom ) is used , in studio the traces are shown as different agent run.

[Nivesh353]

Thanks @utshomax for flagging this. This looks like it originates on the Lyzr Proxy backend side rather than the Studio UI — the trace view just renders whatever trace_id/run_id grouping it receives from the backend; it doesn't do any client-side merging. If the proxy is assigning a new trace_id per LLM call instead of reusing one id for the whole agent execution, that would explain why Studio shows it as separate runs instead of one grouped trace. Worth checking how the proxy assigns/reuses the trace id across successive calls within a single run.