Skip to content

Trace marked successful even when subprocesses fail #748

@jsbroks

Description

@jsbroks

A trace is currently marked as successful even when one or more subprocesses (spans) fail. This leads to misleading trace status and makes failures easy to miss.

Additionally, failure messages reference internal IDs instead of human-readable names, which makes debugging unnecessarily difficult.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions