Skip to content

Unexpected turn structure in W&B Weave trace #7222

Open

Description

@suhaibmujahid

Example: https://forge.coreweave.com/wandb/moz-bugbug/hackbot-dev/weave/agents/conversations/4f4b49fd-ba7f-4860-b538-be0b851755a2

Unexpected turn structure

  • This trace is rooted at the tool or LLM span "chat claude-opus-5-5" instead of an agent (invoke_agent) span. Its parent agent span was never received, so the turn is missing its start and its initiating input. Check that the agent span was exported with the same trace ID.

Weave displays each trace as one turn. Keep the LLM (chat) and tool (execute_tool) spans for a complete exchange under the same agent (invoke_agent) span, in the same trace. Check for missing message content, split traces, or a run that ended early.
Learn how to structure agent spans

Activity

  1. ayoubdiourin7 commented on Oct 18, 2026

    @ayoubdiourin7
    Contributor

    I think the trace isn't broken; the run was still going when this was filed.

    • Run: 11:06–13:19 UTC. Issue filed at 11:29.
    • Weave sends chat and tool spans as they finish, but the root invoke_agent span only when the run ends.
    • So mid-run, the root wasn't there yet, which caused the warning.

    It now shows one complete turn and the warning is gone.

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

Metadata

Metadata

Assignees

Labels

Type

Fields

Priority

Medium

Effort

Low

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions