Cavaliba has an internal scheduler to run various periodic tasks. You have nothing to configure.

The only tasks not handled internally are backup tasks which you should configure on your own (see dedicated doc page).

Current internal tasks

Task	Runs	Does
housekeeping_daily	daily, CAVALIBA_HOUSEKEEPING_SCHEDULE (default 22:22)	maintenance bundle, see below
archive_expired_sirene	every minute	archive expired Sirene messages
iam_autogroup_update	every 2 minutes	recompute automatic group membership
cmt_sample_hour / cmt_sample_day	every minute / 15 minutes	CMT result sampling
cmt_cleanup_raw / cmt_cleanup_hour	every 15 minutes / 5 hours	CMT data cleanup
telemetry_aggregate	every minute	aggregate telemetry events per period, purge raw events
telemetry_sample	hourly, at HH:05	sample object quantities (see Telemetry)

Each run is recorded in the Logs page (action housekeeping.daily, cmt.sample_hour, …). The frequent ones are logged at DEBUG level, so they are kept LOG_KEEP_DAYS_DEBUG days.

housekeeping_daily bundles several maintenance steps, run once a day at CAVALIBA_HOUSEKEEPING_SCHEDULE (default 22:22):

• update_bigset
• EAV refresh, then EAV purge (remove orphan EAV cache rows)
• log purge (per level retention: LOG_KEEP_DAYS_DEBUG / INFO / WARNING / ERROR / CRITICAL, then LOG_MAX_ENTRIES)
• clear expired sessions
• revision purge (REVISION_KEEP_DAYS)
• telemetry purge (per period retention: TELEMETRY_KEEP_DAYS_MINUTE / _HOUR / _DAY / …)
• datatask cleanup (terminal DataTask entries older than 30 days)
• filestore cleanup: delete DataFile entries past their not_after date, along with their backing file, then remove orphan files found in the filestore folder with no matching DataFile record (e.g. leftover temporary upload files) once they are more than 24h old