Guides
Destination archive and restore
Remove a Destination from new fan-out while preserving history, and restore it safely.
On this page
Archiving removes a Destination from new fan-out while preserving its identity, URL, signing secret, and history. It is not a cancellation policy.
Archive
Open the Destination and choose Archive. Provide a short reason and confirm. Users with Owner, Admin, or Developer permission can archive.
Effects:
- no new Events fan out to the Destination;
- it moves out of the ordinary active list;
- its active Destination slot is released;
- existing accepted Deliveries continue with their lifecycle;
- replay is blocked until it is restored;
- history and audit remain.
Archive does not cancel an in-flight retry, dead-letter anything, or delete the signing secret.
Restore
Open the archived Destination and choose Restore.
Restore:
- requires Owner, Admin, or Developer permission;
- clears the archived state;
- preserves the previous enabled/disabled setting;
- rechecks the active Destination allowance;
- writes an audit event.
A restored enabled Destination becomes eligible for new Events immediately. A restored disabled Destination stays disabled until you explicitly enable it.
When to archive vs disable
| Goal | Use |
|---|---|
| Temporarily pause sends but keep the active slot/config | Disable |
| Retire a Destination and free its slot while preserving history | Archive |
| Stop retries for one Delivery | Stop Automatic Retries |
| Retry a failed Delivery | Replay |
Archive is not a bulk stop. Existing Deliveries to that Destination remain governed by their own retry, stop, and replay rules.