---
title: "Refresh stale data in a Data Studio report | Kodalogic"
description: "Why a Data Studio report template can be a day behind, how to force a refresh of the data, and how the freshness setting on each data source decides it."
url: https://kodalogic.com/support/refresh-stale-data
---

[Support](/support)/When something looks wrong

When something looks wrong

# Refresh stale data in a Data Studio report

Data Studio (formerly Looker Studio) caches each data source for fifteen minutes to twelve hours; press Refresh data in the top bar to fetch now, and set Data freshness on the source to change how long the cache lasts.

Web OverviewData as of 07:40Updated just now

Total Users

90,47590,765

Sessions

111,780111,332

Key Events

90,87690,578

Refresh cadenceEvery 12 hours 

## Why the numbers can be a day behind

Data Studio keeps a cache per data source so that opening a page does not query Google every time. Depending on the connector that cache lasts between fifteen minutes and twelve hours, so a report opened in the morning can show yesterday’s numbers until it expires. This is Data Studio, not the template, and it is what keeps a busy report inside Google’s quota.

## Refreshing now

1. 01  
Open the report in view mode.
2. 02  
Press the refresh data control in the top bar: the circular arrow next to the date range, or View, then Refresh data. In edit mode the same control lives in the toolbar.
3. 03  
Every chart on the page fetches fresh numbers. It refreshes this page; other pages refresh when you open them.

## Changing how long the cache lasts

Open the data source (Resource, Manage added data sources, Edit) and look for Data freshness. Shorter values mean fresher numbers and more requests against the Google quota; the default is a good balance for a report clients open a few times a day. A scheduled email fetches fresh data at send time regardless of the setting.

## What no refresh can change

GA4 is not real time in these reports: standard properties finish processing a day’s data up to forty-eight hours later, so the most recent day can change for a while after you refresh. Search Console data arrives with a delay of two to three days by design. Neither is the template; both are how Google delivers the data, and the report says so in the footer of its timeline pages.

## Check

* After Refresh data, the top-right timestamp of the report is now.
* Data freshness on each source is the value you meant, not the shortest one.
* The last two days of GA4 and the last three of Search Console are read as provisional.

## Read the full guide  
This doc covers your copy of the template. These guides cover the topic in full.

* [Master GA4 quota limits with Data Studio templatesHow caching, freshness and the number of charts add up to the quota, and how to stay under it.](/blog/master-ga4-quota-limits-with-looker-studio-templates)
* [Data Studio cannot connect to your data set: 5 fixesWhen a stale page is actually a broken source, and how to tell the two apart.](/blog/looker-studio-cannot-connect-to-your-data-set)
* [Schedule Data Studio dashboards for weekly email deliveryWhy the scheduled PDF always carries fresh numbers, whatever the cache says.](/blog/how-to-schedule-a-dashboard-in-google-looker-studio-for-email-delivery)

## Related

* [No data or errors →](/support/no-data-or-access-errors)
* [No data or access errors →](/support/no-data-or-access-errors)
* [Sharing and scheduling →](/support/sharing-and-scheduling)

Still stuck? [Write to us](/contact): technical support is part of what you bought.

[← All support docs](/support)