# An alert fires at 3am for the orders_daily DAG

Canonical URL: <https://datadriven.io/problems/an-alert-fires-at-3am-for-the-ordersdaily-dag-the-on-call-755524e0>

Domain: Pipeline Design · Difficulty: medium

## Problem

An alert fires at 3am for the orders_daily DAG. The on-call engineer has never seen this pipeline. A wiki page that says 'contact Eric' is not enough; Eric is asleep. The section's runbook has five sections: symptom (what the alert means), impact (who is affected), diagnosis (ordered checks for the likely failure modes), response (the fix for each), and escalation (who to call when the runbook does not resolve). Draft the runbook by adding a runbook artifact downstream of the alert destination whose name names all five sections, plus a link node that ties every alert to the runbook so a CI check catches broken links.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/an-alert-fires-at-3am-for-the-ordersdaily-dag-the-on-call-755524e0)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.