Background jobs & maintenance
Keep reconciliation, notifications and deletion processing running.
On this page
Schedule the jobs
| Job | Endpoint | Intended cadence |
|---|---|---|
| Reconciliation | /api/v1/cron/reconcile | Every minute |
| Anomaly notifications | /api/v1/cron/anomalies | Hourly |
| Weekly digests | /api/v1/cron/digest | Weekly |
| Cleanup | /api/v1/cron/cleanup | Daily |
Configure your scheduler with Authorization: Bearer <CRON_SECRET> using a protected secret. Both GET and POST are implemented. These are operator jobs, not public MCP tools. Never share the scheduler secret with end users or client-side scripts.
Reconciliation
Reconciliation processes delayed work and provider synchronization and attempts bounded backfill of unattributed transactions. It can repair delayed matching where sufficient data exists; it cannot recover visits that were never collected.
Cleanup
Cleanup purges expired sessions/challenges/tokens, runs site deletion and visitor erasure jobs, removes sufficiently old expired invitations, deletes processed non-failed webhook audit rows older than 90 days and API request logs older than 30 days. Failed webhook audit rows are retained by this cleanup rule for investigation.
Monitor failures
Inspect job response status and duration, provider errors, email delivery failures and pending deletion status. A successful web health check does not prove that every scheduled job has completed. Avoid duplicate overlapping scheduler invocations when an external action is still being processed.
Retention is explicit
These audit and token cleanup rules are not an all-data retention guarantee. Review PostgreSQL, ClickHouse and object storage retention and backups separately when operating the service.
Still looking for an answer? Try troubleshooting or get in touch.