Solution skill
Sentry: replay configured but no replays recorded
Complete solution
Shows how to fix sentry: replay configured but no replays recorded. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
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. This is the most common miss: people set the rates and forget the integration. In dev, set the session rate to 1.0 to test (the docs suggest exactly this).
When to use
You are seeing this: replaysSessionSampleRate is set, but issues have no replay attached and the Replays page is empty. Use this skill when you run into "Sentry: replay configured but no replays recorded".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
The symptom
replaysSessionSampleRate is set, but issues have no replay attached and the Replays page is empty.
Checklist, in order
- Integration in the list. The sample rates do nothing without
Sentry.replayIntegration()inintegrations. This is the most common miss: people set the rates and forget the integration. - Rates nonzero.
replaysSessionSampleRate: 0.1samples 10% of sessions;replaysOnErrorSampleRate: 1.0captures 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). - Adblockers. Same story as error events: filter lists block the replay payloads. If replays vanish only for some users, tunnel or proxy the traffic.
- CSP. A strict
connect-srcorworker-srccan block the replay worker and uploads. The console shows the violation; allow the ingest host or your tunnel path. - 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 2 · 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>