> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serviceplan-agents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data areas and refreshes

> How a dashboard gets new figures, how often, and how you manage cadence, delivery and run time.

> [!NOTE]
>
> **In short:** Each series of figures on a dashboard is a **data area**. For each area, it is defined how often new data arrives (**cadence**) and which coworker delivers it. You manage both in the **Overview** tab under **Data**. Every refresh extends the dashboard's run time.

## What a data area is

A dashboard consists of one or more data areas, such as "Prices per week" or "Electricity consumption by region". Each area arrives on its own cadence. Every delivery is stored with its date. That is how the dashboard can show how figures develop over time.

A refresh never changes the design of the dashboard. Only the figures change.

```mermaid theme={"dark"}
%%{init: {'theme':'base', 'themeVariables': {'primaryColor':'#FFF5F5','primaryBorderColor':'#FF4B4F','primaryTextColor':'#141414','lineColor':'#FF4B4F','tertiaryColor':'#ffffff','fontSize':'14px'}}}%%
flowchart LR
    H["A coworker delivers<br/>new data"] --> F["The data area stores<br/>it with its date"]
    F --> D["Your dashboard<br/>shows it"]
    C["Daily display check"] -.-> D
```

## The Data table

In the **Overview** tab, **Data** shows one row per data area. You see:

* when the latest data arrived,
* the next refresh,
* the cadence,
* the cost per run,
* the status.

| Status | Meaning |
| - | - |
| **Up to date** | The area is current. |
| **Overdue** | The next delivery has not arrived. See [When something goes wrong](https://docs.serviceplan-agents.com/en/live-apps/disruption-mails.md). |
| **Paused** | Regular refreshes are paused. |
| **Never updated** | The area has never received data. |
| **On request** | The area is refreshed only when someone asks. That is why it is never overdue. |
| **Calculated** | The dashboard computes the values itself from other areas. |
| **Finished** | You ended the refreshes. The data stays on the dashboard. |

**Refresh now** immediately starts an additional refresh. It costs the same as a regular one. The cadence stays as it is.

> [!NOTE]
>
> **Screenshot needed:** the "Data" table in the Overview tab with cadence, "Delivered by" and the statuses.

## Adjusting a data area

Click the name of a data area to adjust it.

* **Delivery** (*Delivered by*): If you choose a different coworker, the previous refresh ends. Then click **Start the refresh jobs** so that the new coworker delivers.
* **Cadence:** daily, weekly or monthly. The refresh follows the new cadence from its next run.
* **Stop expecting updates:** This permanently ends the refresh of an area. The area then receives no new data and consumes no credits. The most recently delivered data, however, remains visible on the dashboard. With **Expect updates again**, you switch it back on.

### The cadences

| Cadence | Meaning |
| - | - |
| **Every day** | New data daily. |
| **Every week** | New data weekly. |
| **Every month** | New data monthly. |
| **Only when asked** | Regular refreshes pause. **Refresh now** keeps working. |
| **Calculated from other feeds** | The dashboard computes the values itself from other areas, for example a sum or a share. That is why the area is called "calculated". It does not need its own data from a coworker. Its refresh ends. |

If you want a paused area to refresh regularly again, choose a cadence again. The Console then asks for confirmation (*"Run updates again?"*), because credits will be charged again.

> [!TIP]
>
> You can rename individual data areas. You cannot rename the dashboard itself, because its name is part of the fixed link.

## Run time

A dashboard runs for **90 days**. **Every data refresh automatically extends the run time.** If a dashboard stops receiving refreshes, this happens:

1. **Before it expires**, the Console notifies you. The person responsible (owner) receives an email ("Your live dashboard … comes up for renewal"). The badge shows **Expiring soon**.
2. **After it expires**, the dashboard stays online for a short while. The badge shows **Grace period**.
3. **After that**, the dashboard goes offline. Nothing is deleted.

Use **Extend by 90 days** on the dashboard's page to extend the run time manually. A dashboard that is offline can be restored with **Bring this dashboard back**. Links you already shared then work again.

## What you can do next

> [card] [Rules, method and lists](https://docs.serviceplan-agents.com/en/live-apps/feed-guides.md)
>
> What a coworker follows with every refresh.

> [card] [When something goes wrong](https://docs.serviceplan-agents.com/en/live-apps/disruption-mails.md)
>
> No new data or a display error.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.