Allow minReplayDuration to be longer than just 15 seconds

Problem Statement

Currently, minReplayDuration can be configured to be between 5 and 15 seconds
We observe lots of agentic traffic that lasts for like 30 seconds and then goes away.

I don't see a reason to why this should be kept at max 15 seconds
I think that this should be freely configurable, from 1 to 60 or more seconds

Solution Brainstorm

I think this should be possible to do by just tweaking hardcoded values in Code - I did not think about in-browser-storage though

Additional Context

_{Tip: React with 👍 to help prioritize this improvement. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

JS-1122

@SpotlightForBugs

@SpotlightForBugs
fixed it , please let me know!

@naaa760
Oh my god!!!!
That’s awesome!!!!!

@SpotlightForBugs

Hey @SpotlightForBugs, thanks for reaching out.

We observe lots of agentic traffic that lasts for like 30 seconds and then goes away.

I don't understand how a higher minReplayDuration would affect this usecase? minReplayDuration just checks that a replay has a minimum duration, your usecase would not be below this boundary.

@SpotlightForBugs

Hey @SpotlightForBugs, thanks for reaching out.

We observe lots of agentic traffic that lasts for like 30 seconds and then goes away.

I don't understand how a higher minReplayDuration would affect this usecase? minReplayDuration just checks that a replay has a minimum duration, your usecase would not be below this boundary.

Well, I want to only capture like 10% of all replays that are more than 1 minute long - or on error, because I don't want to randomly get the bots or the agentic browsers that just click everything they can and then trash the replay tab - forcing us to manually filter them out.

@chargome

@chargome

@chargome
I don’t get why there would be hard limits.
And it’s way more complicated to do than with just a configurable number.

@billyvg

Replays in buffer mode are stored in memory for 60s, if we would increase this limit this would mean you would drop replays triggered by errors. We could discuss bumping the limit a bit, but def not to 5minutes.

@billyvg any ideas how we could make this usecase more dx friendly?

@chargome

@chargome I get that
I think 35 seconds would be more than enough to filter the vast majority out.

I think 35 seconds would be more than enough to filter the vast majority out.

Generally sounds reasonable to me, we'll just need to check if this might have any side-effects

feat(replay): Bump limit for minReplayDuration (getsentry#18190)

A PR closing this issue has just been released 🚀

This issue was referenced by PR #18190, which was included in the 10.26.0 release.

Navigation Menu

Repository navigation

Allow minReplayDuration to be longer than just 15 seconds #18109

Problem Statement

Solution Brainstorm

Additional Context

3 remaining items

A PR closing this issue has just been released 🚀

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Allow minReplayDuration to be longer than just 15 seconds #18109

Description

Problem Statement

Solution Brainstorm

Additional Context

Activity

linear commented on Nov 6, 2025

nehaaprasad commented on Nov 7, 2025

SpotlightForBugs commented on Nov 7, 2025

chargome commented on Nov 7, 2025

SpotlightForBugs commented on Nov 7, 2025

3 remaining items

SpotlightForBugs commented on Nov 7, 2025

chargome commented on Nov 7, 2025

SpotlightForBugs commented on Nov 7, 2025

chargome commented on Nov 10, 2025

github-actions commented on Nov 19, 2025

A PR closing this issue has just been released 🚀

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions