---
schema_version: "1"
id: 5527ecf0843053f42df50dcab9fac9d2639cc05cc0d8255d6076fed1e1492234
title: Data Drift in Incremental Runs
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_batch_transform_data_drift.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_data_drift.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f9233de118ee8ff04dc33a57eb8f2620d7e1201304c4204177c894267ad26b2c
description: When running a batch data transform in incremental mode, data drift can cause output objects to include changed records instead of filtering them out or replacing them. Data drift is corrected in the daily scheduled ‌full run.
products:
  - Data 360
release: "264"
---
# Data Drift in Incremental Runs

When running a batch data transform in incremental mode, data drift can cause output objects to include changed records instead of filtering them out or replacing them. Data drift is corrected in the daily scheduled ‌full run.

Data drift occurs in these situations.

- When filtering on values to remove records from the output, an updated record isn’t filtered out if the value that was changed now meets the removal criteria. The updated record is filtered out in the next full run.
- If a value in a column that’s mapped to a primary key column changes, the updated record is treated like a new record because the updated record’s generated primary key is different from the original key. In this scenario, the output of the incremental run retains one record with the original generated primary key and one record with the updated key until the next full run.

To correct data drift, a full run occurs every 24 hours.