Retention and Scheduled Purge

Retention and Scheduled Purge

Defaults and individual schedules

Default quarantine retention is 0 days, meaning no default automatic purge. A positive value supplies a purge date based on the original quarantine timestamp. The supported day range is 1–3650.

The quarantine manager supports individual schedule changes, including a delay/date and clearing a schedule. Review the displayed deadline before saving.

Changing the default also updates existing records that follow the default. Explicit manual schedules are preserved. Lowering the default can therefore make older entries immediately due; setting zero should not be assumed to cancel manually scheduled entries. Inspect those individually.

Worker

The installer creates /etc/cron.d/appdata.cleanup.plus. In the reviewed version the worker runs at minute 17 of every hour, using the server's scheduling clock. A due time is eligibility for a subsequent sweep, not a guarantee of deletion at that exact second.

The worker uses normal purge safety validation and the operation lock. If another cleanup owns the lock, it skips safely. Failed scheduled purges pause the failing schedule and record the error for review.

Opening diagnostics or another read-only summary does not trigger cleanup. The scheduled worker, rather than a diagnostics download, is responsible for background expiry.

Operational checks

If an entry has not purged, check its deadline and server time, whether a schedule is actually active, plugin installation/cron presence, operation activity, History and relevant logs. An offline server cannot execute its scheduled work.

Disable or clear unwanted schedules before relying on a longer recovery period. Safe Mode does not cancel purge schedules. Uninstall removes the cron job as described in Installation and Updates.