heartbeat

Heartbeat monitoring confirms agent availability by requiring agents to send real-time heartbeat updates. If an agent stops updating its heartbeat, the dashboard flags the session as offline or stale, preventing tasks from stalling or misrouting.

Fleet health becomes ambiguous because the heartbeat mechanism tells the dashboard and other agents that an agent is alive. Without continuous heartbeat updates, the system cannot confirm agent availability, causing tasks to stall or misroute.

To check fleet readiness, query and monitor the health of all agents to detect offline or stale sessions. This allows you to quickly verify availability and confirm readiness before routing work or issuing commands.

Yes, you can audit task queues and read agent health via the wcc bus commands. The heartbeat mechanism supports health readouts and task queue audits to facilitate proactive offline diagnosis.

You need to start updating your heartbeat immediately after session start to indicate you are online and ready for work. Continuous updates enable proactive offline diagnosis if your agent becomes unresponsive.