Skip to content

Do not start UI event transactions if there already is one on Scope #5491

@romtsn

Description

@romtsn

Description

At the moment we start a UI event transaction and then check if there's already an existing one on Scope - if yes, we do not set the UI event transaction to the Scope. But this makes it redundant anyway, because if the UI event transaction is not on the Scope, it will not have any children, and we do not send such idle transactions without children.

We could improve it and not start the transaction at all if there's something on the Scope already.

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions