> ## Documentation Index
> Fetch the complete documentation index at: https://control.datarelay.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Daily Operations Checklist

> A repeatable operator workflow for dashboard health, Stream/Route drilldown, and evidence collection.

# Daily Data Flow Operations

**Goal:** assess whether critical business data is arriving and being delivered, and identify exactly which Stream/Route requires attention.

> [!NOTE]
>
> **Screen version:** The numbered images are historical Control UI test captures. Follow the current five-step flow (Connect → Sample & Record Selection → Destinations → Route Processing → Deploy), not older step ordering. See the [numbered screenshot guide](https://control.datarelay.run/use-cases/screen-walkthrough.md).

## When to use this scenario

This scenario builds on an existing Connector, Destination and Stream. If you have not configured a Source yet, start from the [connector-specific collection guides](https://control.datarelay.run/use-cases/index.md). Follow the concrete steps below and verify **actual Logs and Destination/quarantine evidence**. Existing test screenshots are illustrative, not runtime proof.

## Before your shift

Know the Stream groups/products you own and the expected incoming event volume/period. Use a Viewer account for observation where possible; edit/Replay actions require authorized roles.

## 1. Review fleet status

1. Open **Dashboard** (`/monitoring`).
2. Record the time window and the overall state: Healthy/Warning/Critical, incoming and outgoing events, and delivery success rate where available.
3. Investigate Streams with no data or low volume. Interpret a zero count against the expected source schedule — quiet sources may be normal.
4. Examine capacity or schema warning indicators, but do not assume aggregated dashboard indicators prove the cause.

![dashboard-triage — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/dashboard-triage.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=f9c658cdeaa4638d8010ca10721745f1)

*Figure 1. **Beginning an investigation on Dashboard.** ① Set the time window, ② inspect Health/Critical, ③ use Recent Alerts for context. Verify the root cause in Streams, Routes and Logs.*

## 2. Drill down to one affected Stream

1. Open **Streams** (`/streams`) and select the relevant product/source group.
2. Find the Stream with abnormal volume or errors; open its runtime/detail view.
3. Confirm Source collection, last run, event extraction, Checkpoint, and current Stream enabled state.
4. Open **Data Flows / Routes** (`/routes`) for the Stream; identify whether a specific Route or Destination is degraded.

## 3. Gather per-Route evidence

1. Open **Logs** (`/logs`) and filter by the exact Stream and Route, time window, stage, and status.
2. Open a failed or suspicious row to record ID, timestamp, cause, and downstream Destination.
3. If delivery failed, follow [Delivery incident response](https://control.datarelay.run/use-cases/delivery-incident.md). If the event was held by policy, follow [Quarantine review](https://control.datarelay.run/use-cases/quarantine-replay.md).
4. Save a local search and export loaded matching rows using [Logs & exports](https://control.datarelay.run/use-cases/logs-audit.md) if formal incident evidence is required.

## 4. Confirm the fix

When an authorized corrective action is taken, trigger or observe a **new** run, compare its exact event/Route identifiers and independent receiver state, and verify any expected Checkpoint effect. Do not interpret a green dashboard alone as proof that the original failed event recovered.

## Completion record

Record: date/time window, Stream group, affected Stream/Route/Destination, error evidence, corrective action, exact run IDs, subsequent receiver proof, unresolved issues and next owner.

**PASS:** every flagged critical data flow has a verified healthy state or a documented, owned incident with supporting Logs. Do not silence/disable alerts merely to make a dashboard green.

**Related:** [Logs evidence](https://control.datarelay.run/use-cases/logs-audit.md), [Schema changes](https://control.datarelay.run/use-cases/schema-change.md), [Route processing](https://control.datarelay.run/processing/route-processing.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.