> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/understand/activity.md).

# Track activity

Activity shows the full execution and change history for a data product. Use it to inspect individual runs, see what changed in recent versions, and find out which models, metrics, and assets were affected.

The Activity tab has two views: **Runs**, which list completed executions, and **Plans**, which list the changes introduced in each version.

## Open Activity

From the data product page, click **Runs** in the Quick access bar, or click **View full run history** in the Trust and freshness section.

## Runs

The Runs view lists every execution of the pipeline. It's how you confirm the product refreshes on schedule and catch failures early.

![Run history trend chart and run list showing run statuses and error details](/files/UXXJKFOxuinJuD3Ol6FQ)

### Run trend chart

The trend chart at the top shows a bar per recent run, so you can spot failures at a glance. Use **Next run** to page through.

### Run list

Scan the recent execution history and pick a run to inspect:

<table><thead><tr><th width="161.45404052734375">Column</th><th>What it tells you</th></tr></thead><tbody><tr><td>Run number</td><td>A sequential identifier (e.g. Run #5) so you can reference it.</td></tr><tr><td>Status</td><td>Succeeded (green check) or failed (red X).</td></tr><tr><td>Time ago</td><td>How recently it ran. Use this to judge whether the data is current.</td></tr></tbody></table>

Click a run to open its detail panel.

### Run detail panel

What happened in a single run:

<table><thead><tr><th width="155.07672119140625">Field</th><th>What it tells you</th></tr></thead><tbody><tr><td>Run number</td><td>Which run you're inspecting, with a status badge (e.g. <strong>Failed</strong>).</td></tr><tr><td>Timestamp</td><td>When the run executed. Use this to correlate with the data you're seeing.</td></tr><tr><td>Duration</td><td>How long it took. Lets you spot abnormal runs.</td></tr></tbody></table>

The detail panel has two tabs: an **Errors** count (or success summary) and **Models evaluated**.

#### Errors tab

When a run fails, the Errors tab lists the failing models. Each entry shows:

* The model name and schema path.
* The error type as a badge (e.g. `UndefinedColumn`).
* An expandable **Error log** with the full message.

![Run detail showing failed models with error badges](/files/bZ902iI36BCgdprJSE75)

![Run error log expanded for a failed model](/files/MgKO2Z6dWoFto8uGTedi)

#### Models evaluated tab

Confirm that each model produced data and passed its checks:

<table><thead><tr><th width="122.19970703125">Column</th><th>What it tells you</th></tr></thead><tbody><tr><td>Model</td><td>Which model the row refers to: name and schema path.</td></tr><tr><td>Kind</td><td>How the model was built (Seed, Full, etc.). Helps explain row count and runtime.</td></tr><tr><td>Rows</td><td>How much data was processed. Lets you spot a model that returned unexpectedly few or zero rows.</td></tr><tr><td>Quality</td><td>Whether the data passed its checks: count of checks passed, or "Not evaluated" if none ran.</td></tr></tbody></table>

![Run detail showing the Models evaluated tab with model names, kinds, rows, and quality status](/files/6uMzED8HwNi6MGSuBakg)

## Plans

The Plans view is the version history. It shows what changed between versions so you can judge whether a recent change might affect what you consume. Each version groups the plans applied to move from one version to the next.

![Plans view showing version history with plans listed by version](/files/ay9vmAW8PtuTNZocIy2G)

### Plans list

Plans are organized by version on the left. Each version shows the plans applied to it with status and timestamp. Click a plan to open its detail on the right.

### Plan detail

A selected plan tells you who made a change, when, and how to trace it back to source:

<table><thead><tr><th width="146.11517333984375">Field</th><th>What it tells you</th></tr></thead><tbody><tr><td>Plan number</td><td>Sequential identifier (e.g. Plan #03).</td></tr><tr><td>Timestamp</td><td>When the change took effect.</td></tr><tr><td>Author</td><td>Who to contact about the change.</td></tr><tr><td>Commit</td><td>The source-control commit behind the change.</td></tr><tr><td>Duration</td><td>How long the change took to apply.</td></tr></tbody></table>

The plan detail is split into expandable sections.

#### Added

Newly introduced assets:

![Plan Added section showing newly added models and fields](/files/SqjhS9matpfApDWYqEMW)

* **Models** - New models added to the data product.
* **Fields** - New columns or fields added to existing models.

#### Removed

Assets removed in this plan, grouped by type.

#### Modified

Assets changed in this plan. Each modified item shows:

* Asset name and schema path.
* A **Breaking** badge if the change is breaking for downstream consumers.
* A **Backfill** badge if the change requires a data backfill.
* An **Impacted** count of downstream assets affected.
* A **Code difference** view: before-and-after SQL or config diff.

![Plan Modified section showing a breaking change with SQL code diff](/files/IjCMhSh4EOWLsEUtAIHp)

For semantic models, a requirements diff and an environment statements diff are also shown.

![Plan showing requirements difference and environment statements difference for a semantic model](/files/9N2iEZITvIP8ZkcocZtn)

#### Impacted

Every asset affected by the changes in this plan, grouped by type. Lets you check whether anything you consume is downstream:

![Plan Impacted section showing affected models, semantic models, metrics, assertions, and quality rules](/files/kF48GpQpjIN72VTwbYE0)

<table><thead><tr><th width="194.46063232421875">Group</th><th>What it tells you</th></tr></thead><tbody><tr><td>Models</td><td>Whether a model you query is downstream of the change.</td></tr><tr><td>Semantic Models</td><td>Whether a semantic model you build queries on is affected.</td></tr><tr><td>Metrics</td><td>Whether a metric you rely on could shift because it depends on changed models or semantic models.</td></tr><tr><td>Assertions</td><td>Assertion configurations referencing the affected assets.</td></tr><tr><td>Quality Rules</td><td>Quality rules running on the affected models.</td></tr></tbody></table>

#### Metadata changes

Assets whose metadata changed without a code change:

![Plan Metadata changes section listing assets with metadata updates](/files/9VFr009I1097GdyKQobA)

#### Backfills

Models that require a backfill after this plan, with the backfill type. Lets you know whether historical figures might shift before you rely on them.

![Plan Backfill section showing models and their backfill types](/files/N8gYRobxxU8NQXLwZH9e)

<table><thead><tr><th width="234.47222900390625">Backfill type</th><th>What it tells you</th></tr></thead><tbody><tr><td>Full</td><td>Every historical value gets recomputed. The entire model is rebuilt from scratch.</td></tr><tr><td>Incremental by time range</td><td>Only figures inside a specific time window may change. Just that range is recomputed.</td></tr></tbody></table>

## When to use Activity

| Question                                | Where to look                           |
| --------------------------------------- | --------------------------------------- |
| Did the data product run recently?      | Runs: run list                          |
| Did a recent run fail, and why?         | Runs: Errors tab                        |
| Which models were evaluated in a run?   | Runs: Models evaluated tab              |
| Did quality change across runs?         | Runs: trend chart                       |
| What changed in a recent version?       | Plans: Added, Removed, Modified         |
| Are any changes breaking?               | Plans: Breaking badge on Modified items |
| Which assets were impacted by a change? | Plans: Impacted                         |
| Do any models need a backfill?          | Plans: Backfills                        |
| Was metadata updated?                   | Plans: Metadata changes                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/consume/understand/activity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.