Collector Offline

A site's collector, such as the Lakeside clinic collector, has stopped sending heartbeats, pausing discovery, scanning and evidence collection for that site.

Updated Aug 15, 2026collectortroubleshooting

Trigger: No heartbeat received from a collector within the expected interval (AIQ-COL-001).
Risk: While offline, the site accrues no fresh evidence; dependent controls move to EVIDENCE GAP rather than failing outright, but assurance confidence for the site degrades the longer the gap persists.

Prerequisites

Confirm whether the outage is planned (maintenance, host replacement) or unexpected
Identify who has physical or remote access to the collector host
Confirm the expected network path from the host to the AssurIQ ingest endpoint

Recommended fix

Confirm the host is powered on and reachable on the local network.
Check the collector service status locally and restart it if stopped.
Verify outbound HTTPS/mTLS connectivity to the AssurIQ ingest endpoint has not been blocked by a firewall or proxy change.
If the mTLS certificate is invalid or expired, re-enroll the collector with a new token.
Confirm the heartbeat resumes in AssurIQ within one collection cycle.

Validation

Collector status returns to Online with a current heartbeat timestamp
Discovery and scan jobs for the site resume on schedule
Dependent controls move out of EVIDENCE GAP as fresh evidence arrives

Rollback and recovery

No rollback is required; if re-enrollment was used, the previous enrollment token should be revoked once the new one is confirmed working.

Evidence generated

Collector heartbeat history showing the outage window and recovery
Re-enrollment record, if a new certificate was issued
Resumed evidence collection timestamps for affected controls

Related controls

Related docs