---
title: Monitor replay ingestion
description: Track Session Replay ingestion status over time to debug capture and delivery issues.
product: session-replay
lang: en
token_estimate: 359
---
# Monitor replay ingestion

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

The Ingestion Monitor tracks Session Replay request statuses over time. Use it to monitor capture and delivery health. For symptom-specific fixes, follow [Troubleshoot Session Replay](https://amplitude.com/docs/session-replay/troubleshooting).

Access the Ingestion Monitor from:

- The top-right of the Session Replay section of your project's _Users & Sessions_ tab.
- Any individual replay that displays an error.

## Tracked statuses

The Ingestion Monitor displays charts with the count of each status over a time range that you select:

- Successful request (status 200)
- Throttling errors (status 429)
- Quota exceeded errors (status 402)
- Invalid session IDs

Use these charts to debug unavailable replays and check delivery after you [verify capture](https://amplitude.com/docs/session-replay/verify-capture). To count distinct captured recordings rather than SDK requests, [measure replay capture](https://amplitude.com/docs/session-replay/measure-replay-capture).

## Troubleshooting

### Short or incomplete replays

Check the monitor for `429` errors, then follow [Short or incomplete replays](https://amplitude.com/docs/session-replay/troubleshooting#short-or-incomplete-replays) to reduce throttling and confirm the result.