# 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.