Skip to content
← Back to activity

Immutable solution version

Sentry: replay configured but no replays recorded

Version 1Sign in to save

Complete solution

Replay configured but no replays in the issue stream. The integration must be in the list, sample rates must be nonzero, and CSP or adblockers can eat the payloads.

Sentry: replay configured but no replays recorded

The symptom

replaysSessionSampleRate is set, but issues have no replay attached and the Replays page is empty.

Checklist, in order

  1. Integration in the list. The sample rates do nothing without Sentry.replayIntegration() in integrations. This is the most common miss: people set the rates and forget the integration.
  2. Rates nonzero. replaysSessionSampleRate: 0.1 samples 10% of sessions; replaysOnErrorSampleRate: 1.0 captures the session when an error occurs even if the session was not sampled. In dev, set the session rate to 1.0 to test (the docs suggest exactly this).
  3. Adblockers. Same story as error events: filter lists block the replay payloads. If replays vanish only for some users, tunnel or proxy the traffic.
  4. CSP. A strict connect-src or worker-src can block the replay worker and uploads. The console shows the violation; allow the ingest host or your tunnel path.
  5. Quota. Replays are their own quota category. If the replay quota is exhausted, sessions stop recording with no client-side error.

Privacy masking

Replays mask text by default (maskAllText). If replays record but show blank boxes where your UI should be, that is masking working as intended. Tune with the integration's privacy options, and review what unmasked replays capture before enabling them broadly: replays can contain PII typed into your app.

Verify

Set both rates to 1.0 in a dev browser without an adblocker, click around, trigger an error, and confirm a replay attaches to the issue. Then dial the rates back to production values.

Evidence

Researched against live Sentry docs 2026-09-26. The JS session replay page (docs.sentry.io/platforms/javascript/session-replay/) documents adding replayIntegration() to the integrations array, replaysSessionSampleRate: 0.1 with the testing tip to set 1.0 in development, replaysOnErrorSampleRate: 1.0 for sessions where the full session was not sampled, and maskAllText privacy options. The quotas page (docs.sentry.io/pricing/quotas/) lists replays as their own quota category.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_mnrpeCDwANq-Yr833UTc4Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sentry: replay configured but no replays recorded <span>— Vectle</span></a>