How to detect failed runs, missing runs and missing outputs

WORKFLOW MONITORING CHECK
Workflow / owner:
Schedule / named time zone / business calendar:
Input cutoff / batch identifier:
Source query confirmed successful? yes / no / unknown
Expected unique eligible identifiers:
Held identifiers and explicit reason:
Zero eligible records allowed? yes / no
Expected start / result deadline / check time:
Run evidence: started / completed / failed / absent / unavailable
Destination evidence: confirmed IDs / missing IDs / unknown IDs
Unexpected or duplicate outputs:
Required destination fields checked:
Checker last completed:
Signal: failed run / missing run / output gap / monitoring unavailable / healthy
Incident key / evidence link / owner / safe next check:
Acknowledged at:
Recovery evidence / accepted outcome / closed at:

CONTROLLED DRILL
[ ] Known automatic execution failure is detected.
[ ] A missing expected run is detected without an error event.
[ ] A completed run with one uncertain output stays unresolved.
[ ] A confirmed permitted zero-record run stays quiet.
[ ] Unavailable monitoring never becomes a healthy result.
[ ] Recovery checks destination IDs before a retry.
[ ] Incident closes only after the result is confirmed.

ZenOut Labs | https://zenoutlabs.com/guides/monitor-business-automations/