> 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/v1/evaluate/track-activity.md).

# Track activity

Activity shows the full execution and change history for a product. Use it to inspect individual runs, see what changed between versions, and find which models, metrics, and assets a change affected. It has two views: **Runs** (completed executions) and **Plans** (the changes in each version).

Open it from the product page: click **Runs** in the Quick access bar, or **View full run history** in the Trust and freshness section.

## Runs

The Runs view lists every execution of the pipeline. It is how you confirm the product refreshes on schedule and catch failures early. A trend chart at the top shows a bar per run so failures stand out; the run list shows each run's number, status (succeeded or failed), and how long ago it ran.

Click a run for its detail panel, which shows the timestamp and duration plus two tabs:

* **Errors:** when a run fails, the failing models, each with an error-type badge (for example `UndefinedColumn`) and an expandable error log.
* **Models evaluated:** confirm each model produced data and passed its checks, showing the model, its kind (Seed, Full, and so on), the row count, and the quality result.

## Plans

The Plans view is the version history: what changed between versions, so you can judge whether a recent change affects what you consume. Plans are grouped by version; select one for its detail, which shows the author, the source-control commit, the timestamp, and expandable sections:

| Section          | What it tells you                                                                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Added / Removed  | Models and fields introduced or dropped in this plan                                                                                                          |
| Modified         | Changed assets, each with a code diff, a **Breaking** badge if it breaks downstream, a **Backfill** badge, and an impacted count                              |
| Impacted         | Every asset affected, grouped by models, semantic models, metrics, assertions, and quality rules, so you can check whether anything you consume is downstream |
| Metadata changes | Assets whose metadata changed without a code change                                                                                                           |
| Backfills        | Models needing a backfill, with type (Full rebuilds everything; Incremental by time range recomputes only a window)                                           |

The **Breaking** badge and the **Impacted** list are the two things to scan if you depend on the product: they tell you whether a change could shift the numbers or shape you rely on.

## Questions this answers

| Question                                       | Where to look                   |
| ---------------------------------------------- | ------------------------------- |
| Did the product run recently, and did it fail? | Runs: run list and Errors tab   |
| Which models were evaluated?                   | Runs: Models evaluated          |
| What changed in a recent version?              | Plans: Added, Removed, Modified |
| Are any changes breaking?                      | Plans: Breaking badge           |
| Which assets were impacted?                    | Plans: Impacted                 |
| Do any models need a backfill?                 | Plans: Backfills                |

Activity, together with [Trust and freshness](/consume/v1/evaluate/trust-and-freshness.md), is how you decide whether the product is actively maintained and safe to depend on before you [activate](/consume/v1/activate/overview.md) it.


---

# 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/v1/evaluate/track-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.