Incomplete/missing replays for non-SPA (MPA)

For non-SPA where there is normal browser navigation: we can lose chunks of the replay if the user navigates quickly in and out of pages. This leads to broken looking replays as we do not capture the follow-up screens because they never get sent at all. This can lead to false dead clicks as well (I'm guessing due to bfcache?).

This can be configured, maybe we need to state this more explicitly in docs, but you can set new Replay({ minReplayDuration: 0 }) to basically disable this check.

Not sure how that would affect dead clicks, though, because these are only sent after the timeout (7s) passed. So you'd simply not get any dead click if moving away before 7s, I think!

(I'm the reporter of this)

I'm may be in the minority here as we have an application that isn't a single page app, but I would suggest finding a way to make this work out of the box with what is the default behavior of a web browser and web page. Ideally without having to adjust a parameter that I may still want to have set to several seconds considering the fact that it (as far as I understand it) has a direct impact on cost.

I just tested this and it didn't actually help. Here is my Sentry.init:

Sentry.init({
  dsn: dsn,
  environment: window.Settings.environmentName,
  release: window.Settings.releaseName,

  integrations: [
    new Sentry.BrowserTracing(),
    new Sentry.Integrations.Replay({
      maskAllText: true,
      // Necessary to make this work with regular browser apps
      // https://github.com/getsentry/sentry-javascript/issues/9301
      // - Aaron, Thu Oct 19 2023
      minReplayDuration: 0
    })
  ],

  tracesSampleRate: 1.0,
  replaysSessionSampleRate: 1.0,
  replaysOnErrorSampleRate: 1.0,

  ignoreErrors: ["AbortError"],
  beforeSend: (event) => {
    if (ignoreEvent(event)) {
      return null
    }

    return event
  }
});

And here's a replay ID: 70816a3030b04ca3aa076791bbff3fdb

Am I doing anything wrong in my config?

Could you provide a link to your replay on Sentry SaaS, then I can take a look. What exactly is not working for you? Is the replay not being sent at all, or is there data missing, ...?

@mydea

@mydea i have a ticket open with support. Details are there. It’s #105109

@billyvg

No update from our end at this point (cc @billyvg just in case you looked into this). We'll post updates here once we get to it

@chargome

Nothing on our end, we were going to prioritize this for this quarter but @chargome is being re-allocated for something else, so it'll have to wait

Navigation Menu

Repository navigation

Incomplete/missing replays for non-SPA (MPA) #9301

75 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Incomplete/missing replays for non-SPA (MPA) #9301

Description

Activity

mydea commented on Oct 19, 2023

aaronjensen commented on Oct 19, 2023

aaronjensen commented on Oct 19, 2023

mydea commented on Oct 20, 2023

aaronjensen commented on Oct 20, 2023

75 remaining items

Lms24 commented on Jan 2, 2025

billyvg commented on Feb 24, 2025

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions