Skip to content

IdleTransaction duration should not exceed final timeout #8504

Closed
@AbhiPrasad

Description

@AbhiPrasad

Right now finalTimeout just sets a setTimeout, but doesn't actually enforce a maximum transaction length. This means there are some scenarios where a transaction has started, but has a super long duration (1 min+).

If we see that a transaction's duration has exceeded the final timeout, we should drop it, because it means that the duration is effectively invalid (didn't respect setTimeout of finalTimeout).

┆Issue is synchronized with this Jira Improvement by Unito

Metadata

Metadata

Assignees

Labels

Package: browserIssues related to the Sentry Browser SDKSync: Jiraapply to auto-create a Jira shadow ticket

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions