> 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/tellius-6.2/data/preparing-your-business-views/scheduling-refresh-for-business-views.md).

# Scheduling refresh for Business Views

Schedule refresh for Business Views in Tellius—sync with dataset updates to keep analytics accurate, up to date, and aligned with real-time data changes.

Scheduling a Business View (BV) refresh ensures your analytics are always aligned with the most up-to-date data from your underlying dataset. When datasets are refreshed regularly—whether daily, hourly, or at other intervals—keeping the BV in sync guarantees that the insights you derive reflect the latest information. This eliminates the risk of working with stale data and helps maintain accurate, real-time analytics.

It helps to keep your data in sync with the underlying source. If the dataset is updated regularly (daily, hourly), ensuring the BV also refreshes means your analytics reflect the latest data.

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/Sie3RynHbOa8CwxiYI3v/image.png" alt="" width="563"><figcaption><p>Refreshing a BV</p></figcaption></figure>

In the above screenshot, the underlying dataset already has a scheduled refresh. If **“Refresh BV with the Dataset refresh”** is toggled on, the Business View updates automatically whenever the dataset does.&#x20;

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/WBdqOnpF2KoGeAi4Cw2P/image.png" alt="" width="563"><figcaption><p>When the underlying dataset has no scheduled refresh</p></figcaption></figure>

In the above screenshot, the dataset indicates **“No refresh scheduled”**, so Tellius cannot offer a toggle for automatically refreshing the BV. Without a scheduled refresh on the dataset, there is no recurring event to tie the BV refresh to.

### Scheduling a dataset refresh

* If you want the Business View to refresh in sync with the dataset, you must first configure a refresh schedule for that dataset. Only then, the **“Refresh BV with the Dataset refresh”** toggle will become available.
* Go to **Data → Prepare**, and select the required dataset from the left pane. Click on the **Schedule** tab to schedule refresh for the dataset.
* Once the dataset refresh is set, revisit the **Schedule** tab under **Data → Business Views**. You should then see the toggle to **“Refresh BV with the Dataset refresh”,** allowing you to synchronize the BV’s data updates with the dataset’s schedule.
* Toggle to switch on the refresh schedule and click on **“Save Changes”** to apply.


---

# 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/tellius-6.2/data/preparing-your-business-views/scheduling-refresh-for-business-views.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.
