A cache is an intermediate store that keeps previously retrieved data available so subsequent queries are faster and gentler on upstream systems. In Central Command, caches store voucher, time, and absence information locally instead of going live against Lexware, Clockify, or Timebutler on every UI action. This improves latency and protects against API limits.
Caches are typically populated by sync jobs. These jobs refresh the data periodically or on demand and flag removed or changed records. The UI preferably reads from the cache and stays usable even when external APIs are temporarily slow or restricted. This is essential for multi-instance operation.
Cache does not mean Lexware becomes unnecessary. On the contrary: the cache is a derivative. Stale data is kept manageable through sync frequency, watermarks, and clear status indicators. For teams this means: fast control in the command center, a reliable source in the upstream system. Without the cache, Central Command would be noticeably slower and more API-intensive with many tenants.
