Choose how often each secondary index refreshes, and let Data 360 rebuild only the portion of an index that changed instead of rebuilding the entire index. Previously, every secondary index was fully rebuilt on a fixed daily schedule. Now incremental rebuilds refresh only changed data, reducing refresh cost and data freshness lag. The scheduler lets you set the refresh frequency that best balances freshness against cost.
Where: This change applies to Data 360 in the Developer, Enterprise, Performance, and Unlimited editions.
When: This feature is available starting in October 2026.
Why: Incremental rebuilds are best suited to engagement data lake objects (DLOs) and objects that change at most every 24 hours. Because refreshing an index consumes credits, refreshing more frequently increases consumption. Choose a refresh frequency that keeps your index fresh enough for your queries without refreshing more often than your data changes.
How: Incremental rebuilds apply automatically to your existing secondary indexes at their current schedule. To view or change the refresh frequency for an index, in Data 360 navigate to the Secondary Indexes app.