Configure capture-client heartbeat retention and payload storage
Under Client Health Monitoring, enable Record client heartbeats. TimeSentry stores a timestamp and item count whenever a supported desktop app, Chrome extension, or Office add-in reaches TimeSentry. These health records are retained for 30 days.
Heartbeat data helps confirm that a capture client is communicating. It does not prove that every activity item became a valid time entry.
Store raw payloadsEnable Store raw heartbeat payloads only when needed for auditing or troubleshooting. Raw metadata can include window titles and document names. It requires heartbeat recording and is also retained for 30 days.
Raw payloads can contain sensitive client or document context. Apply least privilege and confirm that retention is permitted by company and client policy.
Disable storageTurning off heartbeat recording also turns off raw-payload storage. Disabling future collection does not imply immediate deletion of records already within the retention period.
Use health data in diagnosisCompare the affected client's last heartbeat, item count, synchronization history, and the expected activity time. A recent heartbeat with zero items points to a different issue than no heartbeat at all.
Related articles: Understand desktop activity capture and privacy, Install and use the TimeSentry Chrome extension, Troubleshoot desktop, Chrome, Office, and mobile capture.