Freshness and coverage
The pills on the overview, cadences, the full sweep, and why an old graph loses its licence.
A graph is only as current as its last collect, and the overview says so with two pills per connection.
The health pill
- fresh — collected within its cadence.
- stale — past twice its cadence without a successful collect.
- broken — the last three attempts failed; the error is shown beside it.
- never collected — declared, but no collect has landed.
The coverage pill
- complete — every automation and every edge was enumerated.
- complete · n named gaps — complete, except for edges the collector could name but not resolve, listed as gaps.
- automations complete · edges partial or unknown — the collector knows what runs and not everything it touches: a repository not yet connected, a cloud project without a manifest.
Cadence
Each connection re-collects on a cadence by system kind: HubSpot, Google Cloud, n8n and Zapier hourly, repositories daily, six hours otherwise. An hourly poll compares change stamps first and is cheap; a full sweep every 24 hours re-reads everything. Settings → Freshness overrides the cadence per system and can pause collection; the graph stays readable while paused. After a failure the next attempt waits five minutes, doubling up to the cadence, so a revoked token is not retried every minute.
The licence
A graph that was complete a month ago does not license "nothing reads this field" today. A system past its age limit (48 hours by default) keeps its completeness, which is a fact about the last run, and loses its licence to support absence claims, with the caveat licence expired beside the pill. Every tool result and every brief carries whether absence claims are licensed.