Vendor File Late or Missing
Use this runbook when the scheduled vendor extract does not arrive on time, arrives empty, or fails validation before bronze ingestion.
Detection and Triage
- Confirm whether the issue is transport, authentication, vendor-side delay, or malformed content.
- Check the latest successful ingest timestamp and determine which downstream datasets would become stale.
- Mark the affected batch as delayed rather than silently reusing prior data.
Fallback Rules
- Hold the bronze-to-silver promotion if the missing file would make downstream scores materially incorrect.
- Reuse prior-day data only when the metric is explicitly allowed to tolerate staleness and the output is flagged as stale.
- Suppress publication for metrics that depend on the missing payload if no safe fallback exists.
Recovery and Reconciliation
- Ingest the late file into bronze with the original vendor timestamp preserved.
- Re-run silver and gold transformations for the impacted date range.
- Reconcile row counts, freshness markers, and any score deltas before reopening publication.
Related
- bronze-layer-loading — raw-ingest handling patterns