Amplitude Session Replay Not Working
Quick answer
Missing replays are usually a zero or low sample rate, 429 throttling, missing Session Replay ID on events, mismatched keys or device IDs, or blocked requests.
Most likely fix: Check sampling and throttling
How to fix it
Try these in order — the most common fix is first.
1. Check sampling and throttling
- Verify sample rate in code and in Session Replay Settings
- Look for 429 spikes in the Ingestion Monitor and lower the sample rate
Did this fix it?2. Check configuration
- Use matching API keys and device IDs for Session Replay and events
- Initialize only once; ensure events carry [Amplitude] Session Replay ID
- Check the console for Content Security Policy errors
Did this fix it?3. Wait and refresh
- Replays ingested in the last five minutes may need one to two minutes; refresh for live ones
Did this fix it?
Symptoms
Replays are missing, short, have gaps, or show 'temporarily unavailable'.
Why it happens
- Sample rate is 0 or low (Android default is 0)
- 429 throttling at peak traffic
- Second init call desyncs device and session IDs
- Content Security Policy or ad blocker
- Replay older than retention
This guide also covers
- amplitude session replay not working
- amplitude session replay missing
- amplitude replay not recording
Still not working?
If Amplitude keeps failing, you're not alone. See every Amplitude problem users report or the alternatives people switch to.
Done fighting Amplitude? Our small team builds your own Amplitude alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us