> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Usage event timestamp is too far in the past

A usage event's `occurred_at` can't be more than 60 days before Paddle receives the request.

> **Early access (beta): usage-based billing**

---

## Example

```json
{
  "error": {
    "type": "request_error",
    "code": "usage_event_timestamp_too_old",
    "detail": "usage event occurred_at 2026-06-01T12:00:00Z is more than 60 days in the past",
    "documentation_url": "https://developer.paddle.com/errors/usage-events/usage_event_timestamp_too_old"
  },
  "meta": {
    "request_id": "00000000-0000-0000-0000-000000000000"
  }
}
```

## Details

| Attribute | Value |
| --- | --- |
| Status code | 400 |
| Error code | `usage_event_timestamp_too_old` |
| Error message | usage event occurred_at %s is more than 60 days in the past |

## Common causes

- The usage event was sent more than 60 days after the usage happened, for example because it was held in a queue or retried on your side.

## Common solutions

- Send usage events soon after the usage happens, and check for queued or retried events that are being sent late.
- If this is a retry of an event that Paddle already accepted, Paddle still counts the original event. Don't change `occurred_at` to get the retry accepted, because Paddle records that as new usage.
- Usage that's more than 60 days old can't be reported.