Settings retention
Webhooks Pro has one retention policy: how many days of delivery logs to keep before pruning. Everything else (webhook configs, payload templates, settings, transition bindings) lives forever until you delete it.
This page is a quick map of what retention does and doesn't apply to. For the actual setting, see Log retention.
What is retained, and how long
Data | Retention |
|---|---|
Delivery logs | Configurable: 7 / 14 (default) / 30 / 60 / 90 days. Pruned daily. See Log retention. |
Webhook configurations | Forever, until you delete the webhook. |
Payload templates | Forever, until you delete the template. |
Workflow post-function bindings | Forever, until you remove the binding from the workflow. |
Settings values | Forever — just current state, no history. |
Queue rows | Until the delivery fires (typically seconds). Stuck rows cleaned up daily. |
License signing secrets | Forever, until you change or remove them. |
Notice what's not here:
There's no audit log of who changed which setting when. The current value is what's stored.
There's no archive of webhook configurations. Once a webhook is deleted, its history is gone — but its delivery log rows survive until retention prunes them.
There's no retention on the queue. The queue is in-flight state, not durable history.
Where retention lives
Settings → Logs → Log retention.
The page shows a live preview of how many rows will be deleted at the next prune as you change the value. There's also a Prune now button to run the prune immediately rather than waiting for the daily job.
For the full reference, see Log retention.
What gets pruned together
The daily prune deletes log rows older than today − retention. Specifically:
Successful deliveries (2xx, 3xx).
Failed deliveries (4xx, 5xx, Network Error).
Skipped deliveries (license-blocked).
Replays (rows with
sourceLogIdset).
All status types are treated equally. Retention doesn't differentiate by status.
What's NOT covered by Log retention
Concern | Where to handle it |
|---|---|
Long-term archive of every webhook delivery | Send a parallel webhook to an archive sink — see Audit Jira events to S3 or SIEM |
Compliance-grade evidence retention | Receiver-side log with its own retention policy; Webhooks Pro logs are diagnostic-grade |
Queue history (which events were debounced together) | Not retained; the resulting log row is the source of truth |
Webhook configuration history | Not retained; export your webhooks regularly via the Backup tab if you need versioning |
Backup and restore — different from retention
The Settings → Backup tab is export / import, not retention. It lets you:
Snapshot every webhook + payload template into one JSON file.
Restore from a previously exported file (with rename or skip on conflict).
It doesn't touch the delivery log. For the full backup/restore reference, see the Backup tab in the in-app Settings page.
Common questions
"Can I keep some webhook logs longer than others?"
No — retention is tenant-wide. Pick the value that suits your most demanding webhook.
"Can I export delivery logs before they're pruned?"
Not natively today. Workarounds:
Send a parallel webhook to an archive sink for the deliveries you care about.
Increase retention to the longest you can stomach.
Tell us at support@ux-software.com — log export is on the radar; concrete use cases help prioritise.
"Does retention affect Replay grouping?"
Yes. If the parent of a replay chain is pruned, the chain visibly breaks at that point. The remaining rows still work — the link is just lost.
Related
Log retention — the actual setting and its mechanics.
Tenant settings — the hub.
Webhook logs — what gets retained.
Audit Jira events to S3 or SIEM — long-term archive pattern.