# replay-busy

> Your organization, or this server, has too many replay reads running.

`429 Too Many Requests` · `Too many replay reads` · `type: https://docs.dlogify.com/errors/replay-busy`

## When it happens

Replay reads run a limited number at a time, per organization and per server. A request over that limit is refused rather than queued.

## How to fix it

Wait for the seconds in `Retry-After` and try again. The dashboard does this on its own.

## Example

```http
HTTP/1.1 429 Too Many Requests
Retry-After: 1
Content-Type: application/problem+json
```

```json
{
  "type": "https://docs.dlogify.com/errors/replay-busy",
  "title": "Too many replay reads",
  "status": 429,
  "detail": "Too many replay reads are running; retry shortly."
}
```

Source: https://docs.dlogify.com/errors/replay-busy