PayloadPuffin keeps an event, and everything it produced, for a fixed number of days after accepting it. Then all of it goes at once. There is one clock per event, and nothing that happens later resets it.
One window per event
An event expires when your organization's retention has passed since the event was accepted:
expires at = event accepted at + retention daysThe clock starts at acceptance, the receivedAt in the 202 receipt. It doesn't start when a delivery finished, when a retry ran, or when you last read the event. A resend adds an attempt and leaves the expiry where it was.
What expires with the event
When an event expires, PayloadPuffin removes these together:
- The event and the request that created it, including the payload.
- Every delivery of the event, whatever its state.
- Every attempt of those deliveries, with the request and response kept for each one.
"Whatever its state" includes unfinished work. A delivery that is still retrying or held when its event expires stops there. It isn't attempted again and can't be resent, because the payload it would send is gone. A delivery can't outlive the bytes it delivers.
Expiry takes effect at once. An expired event is no longer listed, and reading it, its deliveries, or their attempts answers 404. Removing the stored bytes is cleanup that follows.
Retention belongs to the organization
Every app in an organization keeps data for the same number of days. The console shows the current value under Settings, as Data retention, and notes when a custom agreement set it. Retention changes with your plan or an agreement. No API key or console role can change it.
A change applies to every event that still exists, measured from each event's own acceptance:
| Event age | Change | Result |
|---|---|---|
| 6 days | 7 to 14 days | 8 days remain |
| 13 days | 14 to 7 days | Expires at once |
| 6 days | 14 to 7 days | 1 day remains |
A longer retention doesn't bring back data that was already deleted.
A change applies at once, with one exception. Switching to a plan that keeps events for less time deletes the older events within a minute, after Settings asks you to confirm.
The exception is a subscription that ends. Then the paid plan's longer retention stays in force for as many days as it keeps events, so every event from before the end expires on its own schedule. Settings shows the date and how many days of events will be deleted then. After it, the free plan's retention applies. Choosing a plan before then ends the wait. Plans and billing has the details.
What retention doesn't cover
Idempotency keys have their own window: 24 hours after acceptance, whatever the retention. An event can outlive its key, and a key never keeps an event alive.
Retention also decides how long you can look back. If you need a record of deliveries for longer than your retention, read it through Get an event and store it on your side before it expires.