Cron refers to time-based task scheduling on Unix-like systems. In server environments, cron jobs start scripts at fixed minutes, hours, or days. Central Command uses this pattern for background work: Lexware syncs, Clockify reconciliations, Timebutler updates, notifications, and delivery schedules.
Without cron, users would have to trigger every reconciliation manually. With cron, the cache stays fresh while the UI stays responsive. Jobs should account for gaps between instances, rate limits, and error logs. A well-configured schedule balances freshness against API conservation.
For operations, observability matters: which jobs ran, when, and with what result? Central Command and the server logs provide that information. Cron is invisible but central — the backbone of reliability behind the dashboard and workflows. Anyone who changes times or intervals directly influences the freshness of the entire command layer.
