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

# Monitoring with Data Health

> Turn on a new connection, read its status, and know when to act

Once a connection is set up, you watch it on the **Data Health** dashboard in the Auxia Console.

<Note>
  **Turning a connection on.** File sources (Amazon S3 and Google Cloud Storage) switch on when you click **Start ingestion** at the end of the wizard. For BigQuery, **Enable Ingestion** switches on immediately, while **Enable Later** leaves the configurations **Dormant** until you enable them under **Configuration → Connections → Import Configurations**. A dormant or paused configuration doesn't sync.
</Note>

## Summary tiles

| Tile | What it counts |
| - | - |
| **Active pipelines** | Configurations currently switched on |
| **Functional health** | Share of pipelines running cleanly |
| **Quality health** | Share of pipelines writing rows |

Use the filters — **Needs attention**, **Quality alerts**, **Healthy** — to narrow the list. **Show inactive** includes configurations that are switched off.

## The three status dots

Each row shows three dots, one per [pipeline stage](/data-ingestion/concepts/how-ingestion-works): **Transfer**, **Transform**, **Process**. Each dot reflects that stage's latest run.

| Dot | Meaning |
| - | - |
| 🟢 Green | Ran and finished |
| 🔴 Red | Failed |
| 🟠 Amber | In progress |
| ⚪ Hollow | Not run yet |
| Slate | Handled upstream by another configuration |

<Tip>
  **"Skipped — no new data" is not a failure.** It means the run looked and found nothing new in your source. Repeated skips on a source that *should* have data usually mean the data lands later than the schedule, or the date folder format doesn't match. See your connector's troubleshooting page.
</Tip>

## Functional and quality status

| Functional | Meaning | What to do |
| - | - | - |
| **Healthy** | Running cleanly | Nothing |
| **Attention** | Something is off, but data is moving | Open the detail view and read the run history |
| **Problem** | A stage is failing | Open the failing stage |
| **No runs yet** | Enabled; first scheduled run hasn't happened | Wait for the next scheduled run |
| **Paused** | Switched off | Re-enable it if it should be running |

| Quality | Meaning |
| - | - |
| **Good** | Rows landed on the latest successful run |
| **Watch** | Rows landed, but fewer than expected |
| **Bad** | Zero rows written |

## The detail view

Open a row to see the configuration's source table, cadence, runs over the last 7 days, and the date your data is complete through. Each stage keeps its own run history with the date window covered, row counts, and how many rows your [filters](/data-ingestion/concepts/map-your-data) left out.

## Recovering missed data

A scheduled run can only process the current window. If data was missed — your source landed late, or a run failed — contact your Auxia point of contact to **backfill** the affected date range. Fix the cause first (for example, a wrong date folder format); a backfill re-runs the configuration as it currently stands.


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