Team Health
Team Health turns existing workspace signals into a small, deterministic list of conditions that need attention. It uses bounded operational records and no model tokens.
Read the score, then the cause
Open Settings > Team or Projects > Activity. Healthy means no current issue crossed a threshold, Needs attention means work should be reviewed, and Critical means a connection, approval, trigger, budget, or repeated failure needs prompt action.
- Connections are checked against the exact capabilities granted to the workspace.
- Approvals become stale after 24 hours and critical after their review window expires.
- Failures, completion rate, and cost drift use recent bounded terminal-run windows.
- Hosted budget and Trigger Hub health reuse the same server-authoritative records shown elsewhere.
Use the recommended surface
Most recommendations are navigation actions: reconnect in Integrations, decide in Notifications, inspect Trigger Hub, review History, or check usage. Team Health never changes a model, permission, connection grant, team structure, or budget automatically.
Review a pause
After three consecutive failed or halted terminal runs, an owner or admin with publish authority may review a pause proposal. Type PAUSE AUTOMATION exactly. The server recomputes the current health snapshot, rechecks membership and deployment ownership, pauses only that active deployment, and records a redacted audit event.
Understand scheduling and privacy
Publishing workspace automation enrolls the workspace in the existing ten-minute hosted maintenance tick. Checks run in small batches; a failed check is deferred so it cannot monopolize the queue, and it cannot block trigger delivery or hosted runs. Snapshots contain safe issue summaries and aggregate counts, not logs, prompts, output, credentials, source data, or account identifiers.