Troubleshooting

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").

How to contribute | Edit this page | Create a docs issue | Get support

Account Settings

Organization Settings

Product Walkthroughs

Pricing & Billing

Sentry CLI

Sentry API

Security, Legal, & PII

Concepts & Reference

Troubleshooting

Troubleshooting Session Replay-specific Issues

Replay doesn't match my application

My `canvas` elements aren't getting captured

Replay is slowing down my `canvas`

My custom CSS/images/fonts/media aren't appearing when I view the Replay

Why am I seeing too many or too few rage clicks?

Why can't I see the full HTTP request body or all the headers?

The SDK is slowing down my website.

Using Session Replay increases the bundle size of my application.

I see the message: "A large number of mutations was detected (N). This can slow down the Replay SDK and impact your customers."

Text in the iframe isn't masked

Replay on my browser extension doesn't work

Response data for Apollo GraphQL Client network requests is not captured

`console` calls are triggering replays to record

Clicks are incorrectly resulting in a dead or rage click

Clicks appear in the wrong location