10.29 Release Notes: Aug 15, 2026 - Aug 19, 2026¶

Cost management updates¶

Per-user quotas (General availability)¶

Per-user quotas are now generally available. Per-user quotas let quota admins set monthly and daily credit limits for individual users, and notify users at various configurable thresholds. Quotas can target all users in an account or a tag-filtered subset, and cover both warehouse compute and AI feature domains, including AI Functions, Snowflake CoCo, Cortex Agents, and Snowflake CoWork. For AI features, admins can configure quotas to automatically block AI access for users who reach their AI quota limit and release the block when the cycle resets.

With general availability, the following updates are included:

• Configurable end-user block notifications: When block enforcement is enabled, admins can now control whether blocked users receive an email notification. Pass a second boolean argument to SET_BLOCK_ENFORCEMENT_ENABLED. For example, SET_BLOCK_ENFORCEMENT_ENABLED(TRUE, TRUE) enables enforcement and sends email notifications to blocked users. Going forward, end-user notifications will be disabled by default and admins will have to explicitly enable end-user notifications.
• Monthly or daily notification threshold targeting: Notification thresholds can now be scoped to either the monthly or daily credit limit. Pass 'MONTHLY' or 'DAILY' as the fourth argument to ADD_NOTIFICATION_THRESHOLD.
• ACCOUNT_USAGE.QUOTA_ACCESS_BLOCK_HISTORY view: New account-level view that shows all users blocked across all quotas in the account.
• Faster enforcement propagation: Configuration changes now propagate in approximately 5–10 minutes (previously up to 15 minutes).

The following Public Preview methods have been replaced or removed at general availability:

• GET_ACTIVE_BLOCKS() is replaced by GET_ACTIVE_BLOCKS_V2().
• GET_PER_USER_USAGE_PREVIEW() and SET_REFRESH_TIER() are no longer available. Quota evaluation now occurs within minutes for all accounts; a separate refresh tier setting is not required.

For more information, see Per-user quotas.

Anomaly monitors for cost anomalies (Preview)¶

With this release, Snowflake is pleased to announce the public preview of anomaly monitors. Until now, Snowflake detected cost anomalies for a whole account or a whole organization, which could be too coarse to catch a spike inside a single team or project. An anomaly monitor lets you define your own scope using object tags and service types, so you can monitor a business unit, cost center, or project on its own.

Snowflake attributes consumption to each monitor daily, runs the same detection algorithm against it, and can email a notification list that is specific to that monitor. Each account can have up to 20 monitors, and each monitor tracks either credits or AI credits.

You can work with anomaly monitors using Snowsight or SQL.

• Snowsight: The Anomalies tab in Cost management now includes filters for selecting a monitor, choosing a credit family, and building a scope from tags and service types. You can review the anomalies a scope produces before you save it, and recalculate a monitor after you retag resources.

  For more information, see Work with anomaly monitors in Snowsight.

• ANOMALY_INSIGHTS class: New methods create, update, read, and delete monitors, manage each monitor’s notification list, and test a configuration without saving it.

  For more information, see Work with anomaly monitors.

Release notes change log¶