---
schema_version: "1"
id: 0b943813ea626a26c56bbbd0b141c91db92d4e859acc967f768206af6067f0f2
title: Data Drift in High-Frequency Data Graph Refreshes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_dg_data_drift.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_dg_data_drift.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9510d157b490d8c2ac31e2c299d9e41e8b7d7899aec46270701923029147fd7e
description: When you schedule a data graph to refresh more frequently than once per day, you can experience data drift. Data drift occurs when rapid refresh cycles don’t fully capture or reconcile updates from the source system, causing temporary inconsistencies in the data graph.
products:
  - Data 360
release: "264"
---
# Data Drift in High-Frequency Data Graph Refreshes

When you schedule a data graph to refresh more frequently than once per day, you can experience data drift. Data drift occurs when rapid refresh cycles don’t fully capture or reconcile updates from the source system, causing temporary inconsistencies in the data graph.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

A full refresh automatically runs once every 24 hours and corrects any drift that occurs during more frequent refresh cycles.

## What Causes Data Drift

Data drift can occur when the data graph is refreshed multiple times before a full refresh completes. Common causes include:

- Partial Updates: If records in the source system change several times within a day, not all updates appear in the data graph until the full refresh runs.
- Deleted or Modified Records: Records that are deleted or changed in the source remain in the data graph until the next full refresh reconciles them.
- Complex Relationships:When related data or join keys are updated, mismatched or duplicate nodes can appear in the graph until the full refresh reprocesses all data.
- Hierarchical Dependencies: Drift can also occur when updates arrive for deeper-level nodes before their parent nodes exist in the system. In such cases, child records temporarily appear as unmatched or missing relationships until the parent nodes are processed during the full refresh.

## How Data Drift Is Corrected

A scheduled daily full refresh reprocesses all data from the source and realigns the graph with the most recent state of your data. This process removes any inconsistencies, duplicates, or outdated records that appear during high-frequency refresh cycles. As a best practice, use higher-frequency refreshes only when near-real-time data is required and temporary inconsistencies are acceptable.