Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

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

Copy link
Copy link

Description

@romtsn
Issue body actions

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.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status
    Waiting for: Product Owner
    Show more project fields

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.