Daily report stale-data failure
Report run observed; freshness proof missing.
The report ran, but data freshness or delivery proof is missing.
What this demo is / is not
- Simulated example: static scenario data for reading the proof loop.
- Safe demo data: no customer data, provider calls, or live workflow inspection.
- Not connected: it does not inspect your workflows.
- Real proof: real proof requires connecting or configuring Make, n8n, or Zapier.
Observed trigger to missing proof
This static demo stops at the missing-proof state and names the safest next check.
Observed trigger
Scheduled report trigger ran at the expected time.
Missing downstream proof
Quiet failure boundary
No updated sheet timestamp, dashboard refresh marker, or delivered report artifact is present.
Exact next action
Proof / next action
Inspect the data-refresh step before the send/publish step, then verify the final artifact timestamp.
Missing proof
This scenario has no downstream evidence yet.
Proof found
Not claimed in this static demo.
Observed evidence
Scheduled report trigger ran at the expected time.
Missing proof
No updated sheet timestamp, dashboard refresh marker, or delivered report artifact is present.
Inferred risk: Operators may be reading yesterday's numbers while assuming the report is current.
Next action
Inspect the data-refresh step before the send/publish step, then verify the final artifact timestamp.
Recovery should only be treated as proven after downstream evidence exists.
Technical demo assets
Optional repo docs for operators who want the sample workflow spec and JSON payloads. These are demo assets, not hosted provider proof or required reading.
Repo path: docs/demo-workflows/daily-report-stale-data-failure/README.md
Sample JSON and workflow files
workflow.mdsource-event.sample.jsonobserved-evidence.sample.jsonmissing-proof.sample.jsonexpected-diagnosis.sample.json
Diagnosis loop details
- Diagnosis
- Report run observed; freshness proof missing.
- Proof
- Scheduler event exists; data refresh and final delivery evidence are absent.
- Next action
- Check the sheet/dashboard refresh boundary before trusting the report output.
Provider-specific note
The same proof pattern can be modeled for Make, n8n, or Zapier. Provider capability levels differ, so this page avoids provider-parity and automatic recovery claims.