# Health-check every connection in one pass

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Every platform's health check run together: the morning coffee of agent operations.

**Intent.** Which connections are alive, degraded or dead, before work starts.

## When to use

- Start of a session.
- After any OAuth or token event.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: any connected source

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Run each platform's health check. — tools: `google_ads_health_check`, `meta_health_check`, `tiktok_health_check`, `pinterest_health_check`, `ga4_health_check`, `gsc_health_check`
2. Report per platform: healthy, degraded, needs human reconnection.

## Decision rules

- **When** A health check fails on auth → **conclude** Reconnection is a human step by design: hand back with the dashboard link, do not retry into a lockout.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- A passing health check does not guarantee scopes for every tool: it proves the connection, not the permissions.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.