> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/data/preparing-your-datasets/scheduling-refresh-for-datasets.md).

# Scheduling refresh for datasets

Schedule automated dataset refreshes, manage linked updates, and receive delivery reports to keep your data, dashboards, and Business Views accurate and up to date.

Scheduling a refresh keeps your dataset current without manual updates. It ensures your data—and any linked dashboards or business views—stay accurate, aligned, and ready for decisions in real time.

1. Under **Data → Prepare → Schedule**, you can find the following window for scheduling the refresh of the selected dataset.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/vFejHHoUMhyFk62JUB6v/image.png" alt="" width="563"><figcaption><p>Scheduling refresh for file-based dataset</p></figcaption></figure>

* **Refresh Mode**: **R**eplaces existing data with new data. Overwrites the old dataset.
* **Linked Datasets**: If enabled, refreshing this dataset also refreshes any child or derived datasets that depend on it.

{% hint style="info" %}
Large parallel refreshes can overload the system, so recommended practice is refreshing key datasets individually or in a controlled manner.

**“Linked datasets”** can auto-refresh if the parent dataset changes, but this is often turned off by default to avoid a chain reaction of massive refreshes.
{% endhint %}

* **Refresh all BVs with Dataset refresh**: If enabled, any Business View built on this dataset gets refreshed automatically.
* **Drag & Drop a File**: For file-based datasets (CSV, XLSX, etc.) you can upload a new version in the same schema to refresh content (limit up to 2GB). Click on **Upload** to manually trigger an upload process for the replacement data.
* **Schedule refresh:** For other datasets, you can perform an instant refresh, schedule a one-time or periodic refresh. For more details, check out [this](/data/refreshing-a-datasource.md) page.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/fSewqks0g3jIolgcSgYk/image.png" alt="" width="563"><figcaption><p>Schedule refresh</p></figcaption></figure>

* **Delivery Report:** If enabled, sends a delivery report for the refresh task. Provide the following details:
  * **To:** Specify the recipient(s) of the email (mandatory).
  * **CC/BCC:** Add additional recipients if needed.
  * **Subject:** Enter a subject for the email notification (mandatory).
  * **Email Message:** Provide additional details or notes to include in the delivery report.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.tellius.com/data/preparing-your-datasets/scheduling-refresh-for-datasets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.