Excessive Auto-Clustering costs occur when tables experience frequent and large-scale modifications ("high churn"), causing Snowflake to constantly recluster data. This leads to significant and often hidden compute consumption for maintenance tasks, especially when table structures or loading patterns are not optimized. Poor clustering key choices, unordered data loads, or frequent full-table replacements are common drivers of unnecessary Auto-Clustering activity.
Assess whether tables experiencing high churn are critical for business performance or could tolerate less aggressive clustering