> For the complete documentation index, see [llms.txt](https://docs.seemoredata.io/external-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seemoredata.io/external-docs/fundamentals/our-features/waste-reduction/unused-data-flows.md).

# Unused Data Flows

## Overview

Unused Data Flows highlights tables that have **active pipeline connections writing data into them** but **zero read activity** over the analysis window.\
The upstream pipeline compute (dbt runs, Airflow tasks, Fivetran syncs) that feeds these tables is wasted spend.

{% hint style="info" %}
**Required role to configure usage exclusions:** [Editor](/external-docs/fundamentals/settings/user-roles.md) or higher.

Users with lower roles can view insights and mark them as Done, but cannot change account-wide usage exclusions.
{% endhint %}

***

## How It Works

### Detection Logic

Seemore checks two conditions for every table with at least one upstream pipeline:

1. **Active pipeline connection** — the table appears as a destination in a tracked pipeline that has run within the analysis window.
2. **Zero reads** — no SELECT queries have been executed against the table during the same period.

Tables meeting both criteria are flagged as unused data flows.

***

### Upstream Lineage Analysis

For each flagged table, Seemore traces the full upstream lineage to identify:

* **All pipeline steps** that contribute to populating the table.
* **Associated compute cost** of those pipeline runs.
* **Related tables and views** that exist solely to feed the unused destination.

This helps you understand the total blast radius of removing the data flow.

***

### Cost Estimation

Each insight includes:

* **Estimated annual compute savings** from stopping the pipeline.
* **Row count reduction** and **storage freed** by dropping the destination table.

***

## Remediation

1. Verify with the table owner that no downstream consumers exist outside of Seemore's visibility.
2. Disable or remove the pipeline step that writes to the table.
3. Optionally drop the destination table to reclaim storage.
4. Mark the insight as **Done** in Seemore.

***

## Configuration

| Parameter       | Default | Description                                                     |
| --------------- | ------- | --------------------------------------------------------------- |
| Analysis window | 21 days | How far back Seemore looks for read activity and pipeline runs. |

{% hint style="info" %}
If you have configured **Exclude Users from Usage**, excluded users' reads are ignored. This means tables read only by service accounts or bots will still appear as unused data flows.
{% endhint %}


---

# 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://docs.seemoredata.io/external-docs/fundamentals/our-features/waste-reduction/unused-data-flows.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.