Manage data retention and run the purge
Retention sets how long price ticks and expired sign-in sessions are kept, through a change request, and runs the purge (preview first). Audit, ledger and authentication-event records are never purged.
Have questions or need step-by-step guidance on this topic?
Step-by-Step Procedure
Open the page
Open "Platform Configuration" and click "Retention" (address /admin/config/retention). The tiles show the days kept for "Price ticks" and "Expired sign-in sessions"; DEFAULT means no change has been activated yet.
Propose a new period
Click "New Record", pick the "Setting", enter "Days to keep" within the allowed range and a "Reason". A second super administrator approves and you activate the request with the row buttons "Approve" and "Activate".
Preview
Click "Dry-run purge". The message lists how many rows are older than the period in each table; nothing is removed and the run is recorded.
Purge
Click "Run purge now" and confirm. At most 50,000 rows per table are removed per run; the message says how many were removed and how many remain for the next run. It cannot be undone.
The retention period is changed through a four-eyes request, and the purge removes only what is older than the period, with the run recorded in the job ledger.
Troubleshooting & Failure Modes
Was this guide helpful?
Help us refine our platform documentation