Offline cache refers to the locally held data set from which the interface reads, without sending every click live to external APIs. In Central Command, sync jobs feed this data set. The UI thus stays responsive even when Lexware or Clockify are currently slow to answer.
Offline does not mean "without updates." It means "reading from the last known good state." Indicators in the dashboard explain freshness. Watermarks and timestamps help detect stale situations. For multi-instance setups, an offline cache is practically indispensable.
The offline cache protects APIs and users' time at once. It is an architectural decision: control before raw latency. Anyone interpreting values should keep the sync age in mind. Central Command makes this trade-off transparent and leaves Lexware untouched as the source.
