> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).
>
> To search these docs, send a `GET` request to `https://paddle-docs-retrieval.kapa-paddle.workers.dev/?q=<question>` with a URL-encoded question. No authentication needed. It returns a JSON array of `{content, source_url}`, most relevant first.

# Only event notifications can be replayed

The notification can't be replayed because its `origin` isn't `event`.

---

## Example

```json
{
  "error": {
    "type": "request_error",
    "code": "notification_replay_invalid_origin_type",
    "detail": "Only notifications with the origin `event` can be replayed.",
    "documentation_url": "https://developer.paddle.com/errors/notifications/notification_replay_invalid_origin_type"
  },
  "meta": {
    "request_id": "00000000-0000-0000-0000-000000000000"
  }
}
```

## Details

| Attribute | Value |
| --- | --- |
| Status code | 400 |
| Error code | `notification_replay_invalid_origin_type` |
| Error message | Only notifications with the origin `event` can be replayed. |

## Common causes

- When you replay a notification, Paddle creates a new notification entity for the replay with an `origin` of `replay`. You can't replay a replay, only the initial notification related to an event.
- The notification's `origin` isn't `event` — it may be a replay or another notification type.

## Common solutions

- Replay the initial notification related to the event, where the `origin` is `event`.
