Job health

Outcome: identify which scheduled work completed its business purpose, what is late/failed/partial, and whether intervention or a developer handoff is needed.

Scope and impact

Resolve instance/site and a fixed UTC interval with config_inspect (CLI: b2c setup inspect). Obtain the expected jobs, schedule/timezone, and intended updates from the user or available configuration. No matching execution is "missing" only when a run was actually expected. Record the business deadline, affected data/sites, and owner. For material impact, use the team's incident severity/update process; a routine review need not declare an incident. Do not invent impact from a red status alone.

Access and tools