Daily operations

Running PDQ day to day is a short, repeatable routine: confirm that every scheduled extraction, data lake movement, warehouse load and quality check has done its job — and act on the ones that did not.

The routine is deliberately proactive. Nothing here waits for a user to report missing data. The target is to have every delivery and processing step verified before the daily deadline, typically 08:00, Monday–Saturday.

Start here

The daily pass	The routine itself — what to check in INGEST, DLS and DWA, in what order, and what each metric has to say before you sign off.
DataOps Console	Page-by-page reference for the console: what every view shows, what each number means, and which corrective actions it offers.
Troubleshooting	What to do when a check fails — infrastructure, ingestion, processing and warehouse loading issues, with the resolution for each.

What the routine covers

Six checks, in order, following the data from the source outwards: System Health, INGEST Tasks, DLS Trace, DWA Loading Tasks, DWA Additional Tasks, QPI Monitor. Each is set out in full in The daily pass.

Five of the six have a checklist view that compares configured against executed. That comparison is the only thing that catches work which never started — a failure count alone will always read zero for a task that was never scheduled.

Before you assume a failure

Most "empty" pages in the console are answering correctly for a window that is too narrow. Check the global date range first; it defaults to the last 24 hours.

DWA loading tasks are idempotent — rerunning one cannot duplicate or corrupt data. Restarting a failed loading task is the normal first response, not a last resort.