Skip to content

voice: voice.adapter.disconnect span lands on a detached trace id, not the scenario's trace #993

Description

@drewdrewthis

The disconnect span (which carries voice.twilio.stream_ended_reason, frames_received, speech_gate.* counters) is emitted after the scenario trace has ended and is exported under its own trace id (dev run scenariorun_0007chJwsufAHGUoXsb63INYosdUr: run trace 177f9a07651f86653cd54c9de7b1077c, disconnect span on 549381b74304063610e5180e37d4805d, 15 s after the verdict). All 77 disconnect spans on the dev stack behave the same.

Proposal: capture the run's trace context at connect and start the disconnect span under it (or stamp the counters on the last adapter call span).

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions