# Scheduled Reloads

## How scheduled reloads work

Scheduled reloads refresh the data behind your Metrics and Experiments from your warehouse on a daily cadence. Control these reload settings on each entity, or set project-level defaults that entities inherit from in your Project Settings. You can also use the Console API to [trigger experiment result loads](https://docs.statsig.com/console-api/introduction#post-/experiments/-experiment_id-/load_pulse). The Console API is useful for triggering refreshes when your data pipelines are ready.

{% figure %}
<img src="https://docs.statsig.com/images/statsig-warehouse-native/connecting-your-warehouse/scheduled-reloads/d056be8d-19a0-43ae-91e1-cf5e16d23b53.png" alt="Project-level scheduled reload settings interface" width="1443" />
{% /figure %}

{% figure %}
![Individual experiment pulse scheduling interface](https://docs.statsig.com/images/statsig-warehouse-native/connecting-your-warehouse/scheduled-reloads/efc232e7-4189-4ee7-b35a-5b1530041c70.png)
{% /figure %}

## Gate/experiment Pulse scheduling

For feature gates and experiments, you can configure individual Pulse scheduling separately from the project-level settings. Schedule daily Pulse metric reloads for individual feature gates and experiments.

To access this feature:

1. Navigate to your feature gate/experiment in the Statsig Console
2. Go to the Pulse Results tab
3. Use the scheduling controls to configure daily reloads

The scheduling allows you to:

* Set a daily reload time in UTC
* Choose between Full and Incremental reload types
* Save, edit, or cancel scheduled reloads

Individual Pulse scheduling requires gates with partial rollout rules and overrides project-level settings.