ドキュメント変更履歴 2026-08-26

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents@@ -60,26 +60,394 @@ When creating an agent, we recommend selecting **auto** for the model. With this option, Cortex automatically selects the highest quality model for your account, and quality improves as new models become available. -Cortex Agents supports the following models. These models run through [cross-region inference](/user-guide/snowflake-cortex/cross-region-inference), so availability is shown by georegion (the routing scope set by the `CORTEX_ENABLED_CROSS_REGION` account parameter), not by individual region. A model is available to your account when your cross-region routing includes a georegion that's marked for that model.--| Provider  | Model                      | Status         | Cross Cloud (any region) | AWS US | AWS US Gov | AWS EU | AWS APJ | AWS AU | Azure US | Azure EU | Google Cloud US |-| --------- | -------------------------- | -------------- | ------------------------ | ------ | ---------- | ------ | ------- | ------ | -------- | -------- | --------------- |-| Anthropic | `claude-opus-5`            | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-opus-4-8`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-opus-4-7`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-opus-4-6`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-opus-4-5`          | GA             | %cm%                     | %cm%   |            | %cm%   |         |        |          |          |                 |-| Anthropic | `claude-sonnet-5`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-sonnet-4-6`        | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-sonnet-4-5`        | GA             | %cm%                     | %cm%   | %cm%       | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-4-sonnet` (legacy) | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    |        |          |          |                 |-| Anthropic | `claude-haiku-4-5`         | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| OpenAI    | `openai-gpt-5.4`           | Public preview | %cm%                     |        |            |        |         |        | %cm%     | %cm%     |                 |-| OpenAI    | `openai-gpt-5.2`           | GA             | %cm%                     |        |            |        |         |        | %cm%     | %cm%     |                 |-| OpenAI    | `openai-gpt-5.1`           | GA             | %cm%                     |        |            |        |         |        | %cm%     | %cm%     |                 |-| OpenAI    | `openai-gpt-5`             | GA             | %cm%                     |        |            |        |         |        | %cm%     | %cm%     |                 |-| OpenAI    | `openai-gpt-5-mini`        | GA             | %cm%                     |        |            |        |         |        | %cm%     |          |                 |-| OpenAI    | `openai-gpt-4.1` (legacy)  | GA             | %cm%                     |        |            |        |         |        | %cm%     |          |                 |-| Google    | `gemini-3.1-pro`           | Public preview | %cm%                     |        |            |        |         |        |          |          | %cm%            |-| Google    | `gemini-3.5-flash`         | GA             | %cm%                     |        |            |        |         |        |          |          | %cm%            |+Cortex Agents supports the following models. These models run through [cross-region inference](/user-guide/snowflake-cortex/cross-region-inference), so availability is shown by cross-region routing scope (the value of the `CORTEX_ENABLED_CROSS_REGION` account parameter), not by individual region. A model is available to your account when your routing scope is marked for that model. Columns match the scopes listed in [](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-llm-availability) and [](/user-guide/snowflake-cortex/cortex-rest-api#label-cortex-complete-llm-model-availability).++<div className="colwidths-given">++  <colgroup>+    <col style={{width: "7.0%"}} />+    <col style={{width: "15.0%"}} />+    <col style={{width: "8.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+    <col style={{width: "5.0%"}} />+  </colgroup>+  <thead>+    <tr>+      <th>Provider</th>+      <th>Model</th>+      <th>Status</th>+      <th>Cross Cloud (Any Region)</th>+      <th>AWS Global (Cross-Region)</th>+      <th>AWS US (Cross-Region)</th>+      <th>AWS US Commercial Gov (Cross-Region)</th>+      <th>AWS US FedRAMP High Plus (Cross-Region)</th>+      <th>AWS US DoD (Cross-Region)</th>+      <th>AWS EU (Cross-Region)</th>+      <th>AWS APJ (Cross-Region)</th>+      <th>AWS AU (Cross-Region)</th>+      <th>Azure Global (Cross-Region)</th>+      <th>Azure US (Cross-Region)</th>+      <th>Azure US FedRAMP High Plus (Cross-Region)</th>+      <th>Azure EU (Cross-Region)</th>+      <th>Google Cloud US (Cross-Region)</th>+    </tr>+  </thead>+  <tbody>+    <tr>+      <td>Anthropic</td>+      <td>`claude-opus-5`</td>+      <td>GA</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>Anthropic</td>+      <td>`claude-opus-4-8`</td>+      <td>GA</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>Anthropic</td>+      <td>`claude-opus-4-7`</td>+      <td>GA</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>Anthropic</td>+      <td>`claude-opus-4-6`</td>+      <td>GA</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>Anthropic</td>+      <td>`claude-opus-4-5`</td>+      <td>GA</td>+      <td>%cm%</td>+      <td>%cm%</td>+    ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-evaluations+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-evaluations@@ -7,5 +7,5 @@ This feature is not available in the People's Republic of China. -Use this topic for **batch evaluations** of **native Cortex Agents** in Snowflake (Snowsight **Evaluations** tab or `EXECUTE_AI_EVALUATION`). For **live** conversation logs and the **Monitoring** tab, see [](/user-guide/snowflake-cortex/cortex-agents-monitor). For **custom AI applications** evaluated with TruLens, see [](/user-guide/snowflake-cortex/ai-observability/evaluate-applications-trulens).+Use this topic for **batch evaluations** of **native Cortex Agents** in Snowflake (Snowsight **Evaluations** tab or `EXECUTE_AI_EVALUATION`). For **live** conversation logs and the **Observability** tab, see [](/user-guide/snowflake-cortex/cortex-agents-monitor). For **custom AI applications** evaluated with TruLens, see [](/user-guide/snowflake-cortex/ai-observability/evaluate-applications-trulens).  Cortex Agent evaluations allow you to test, baseline, and hill climb on your agent's behavior and performance, so that you know when your agent is ready to roll out to your users. Evaluate your agent against both ground truth and reference-free evaluation metrics. During evaluation, your agent's activity is traced and monitored so you can ensure that each step advances towards your end goal. Per-record **Trace details** in the Evaluations UI match the trace information described in [agent monitoring](/user-guide/snowflake-cortex/cortex-agents-monitor#label-cortex-agent-log-info).@@ -33,4 +33,5 @@ - The USAGE permission on the database and schema containing your agent - The USAGE permission on the database and schema containing your evaluation data+  - If creating the input table that holds your evaluation inputs, CREATE TABLE ON SCHEMA   - If creating a dataset from an input table, CREATE DATASET ON SCHEMA - The following permissions on the current database and schema, which is where the evaluation will be run from:@@ -38,4 +39,5 @@   - CREATE FILE FORMAT ON SCHEMA   - CREATE TASK+  - If creating the stage that holds your evaluation configuration file, CREATE STAGE ON SCHEMA  In Snowsight, agent evaluations are run on the database and schema of the agent. With SQL, agent evaluations are run on the session's database and schema.@@ -52,4 +54,6 @@  Before starting a Cortex Agent evaluation, prepare a table containing your evaluation inputs. This table is used to create a dataset for your evaluation to run against. To learn more about datasets on Snowflake, see [](/developer-guide/snowflake-ml/dataset).++Creating this table requires CREATE TABLE ON SCHEMA, and creating a dataset from it requires CREATE DATASET ON SCHEMA. For the full list, see [](#label-agent-evaluation-access-control).  ### Cortex Code@@ -155,5 +159,5 @@ Both metrics read the `ground_truth_invocations` key in the ground truth VARIANT. The value is an array of JSON objects, one per expected tool-related check. Use the empty array `[]` when you expect **no** tools to be called. Each metric uses this key differently: -- **Tool selection accuracy (TSA)** compares the tool **names** you list in ground truth to the tool names the agent actually invoked. Agents can call tools in parallel or in multiple valid orders, so ordering is not considered. For each record, Snowflake counts how many expected tool names are matched to actual invocations (each actual call is matched at most once), using the formula `matched tools / max(number of expected tool entries, number of actual tool calls)`. This penalizes every failure mode: too few calls, too many calls, or the wrong tools.+- **Tool selection accuracy (TSA)** compares the tool **names** you list in ground truth to the tool names the agent actually invoked. Agents can call tools in parallel or in multiple valid orders, so ordering is not considered. For each record, Snowflake counts how many expected tool names are matched to actual invocations (each actual call is matched at most once), using the formula `matched tools / max(number of expected tool entries, number of actual tool calls)`. This penalizes every failure mode: too few calls, too many calls, or the wrong tools. TSA scoring is deterministic. - **Tool execution accuracy (TEA)** scores the **input and output quality** of the tool calls you describe in ground truth. For each entry, Snowflake finds the closest semantic match among the agent's actual invocations for that tool (pairing each tool call at most once), then scores how well the expected input and output align with the real invocation. An expected tool the agent never invoked scores 0.0 and lowers TEA. Extra tools the agent invokes beyond your ground truth don't penalize TEA (rely on TSA for this instead), and tools of a type that TEA doesn't support are skipped and left out of the score entirely. @@ -289,4 +293,6 @@ You can also run an evaluation through [Cortex Code](/user-guide/cortex-code/cortex-code). Use the `evaluate-cortex-agent` sub-skill of the Cortex Code `cortex-agent` skill in the CLI (see [Cortex Code CLI - Skills](/user-guide/cortex-code/extensibility#label-extensibility-skills)), or continue the same Cortex Code flow from **Prepare an evaluation dataset** in %sf-web-interface% directly into running the evaluation against your dataset. +The skill accepts the same choices as the other paths, including which [agent version](#label-cortex-agent-evaluation-yaml-spec) to evaluate and which [metric versions](#label-agent-evaluation-metric-versions) to score with.+ ### %sf-web-interface% @@ -317,8 +323,9 @@ 7. In the **Name** field, provide a name for your evaluation. This name should be unique for the agent being evaluated. 8. Optional: In the **Description** field, provide any comments for the evaluation.-9. Select **Next**.-   This advances to the **Select dataset** modal.--10. Select the dataset used to evaluate your agent. You can choose either **Existing dataset** or **Create new dataset**.+9. From the agent version dropdown, select the version of the agent to evaluate. The list includes the agent's committed versions, its aliases, and its live version. For guidance on which to pick, see [](#label-cortex-agent-evaluation-yaml-spec).+10. Select **Next**.+    This advances to the **Select dataset** modal.++11. Select the dataset used to evaluate your agent. You can choose either **Existing dataset** or **Create new dataset**.     To use an existing dataset: @@ -333,22 +340,23 @@     4. In the **Dataset name** field, enter your dataset name. This name needs to be unique among the schema-level objects in your selected schema. -11. Select **Next**.+12. Select **Next**.     This advances to the **Select metrics** modal. -12. From the **Input query** list, select the column of your dataset which contains the input queries.-13. For each of the **System metrics**, change the toggle to active for any metric you want included in your evaluation. Select the column of your dataset containing the ground truth for your evaluation.-14. (Optional) To conduct a custom evaluation, toggle on **Custom metrics**.--15. Select the database and schema containing the stage where your custom evaluation configuration is stored.-16. Select the stage where your custom evaluation configuration is stored.-17. Select the YAML configuration file for your custom evaluation.---    In %sf-web-interface%, only the custom evaluation definitions are loaded from your YAML configuration. The rest of the YAML file must still be valid. For the evaluation YAML specification, see [](#label-cortex-agent-evaluation-yaml-spec).---18. For each custom metric, change the toggle to active if you want it included in your evaluation. Select the column of your dataset containing the ground truth for this evaluation.--19. Select **Create** to create the ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api@@ -317,17 +317,19 @@    <colgroup>-    <col style={{width: "30.4%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />-    <col style={{width: "5.8%"}} />+    <col style={{width: "30%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />+    <col style={{width: "5%"}} />   </colgroup>   <thead>@@ -342,4 +344,6 @@       <th>AWS EU (Cross-Region)</th>       <th>AWS APJ (Cross-Region)</th>+      <th>AWS JP (Cross-Region)</th>+      <th>AWS AU (Cross-Region)</th>       <th>Azure Global (Cross-Region)</th>       <th>Azure US (Cross-Region)</th>@@ -363,4 +367,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -378,4 +384,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -393,4 +401,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -403,5 +413,7 @@       <td></td>       <td>%cm%</td>-      <td></td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -423,4 +435,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -433,5 +447,7 @@       <td></td>       <td>%cm%</td>-      <td></td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -449,4 +465,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -464,4 +482,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -479,4 +499,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td></td>       <td></td>       <td></td>@@ -494,34 +516,6 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`openai-gpt-5.6`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`openai-gpt-5.5`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -531,16 +525,18 @@     <tr>       <td>`openai-gpt-5.4`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>     </tr>     <tr>@@ -554,4 +550,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>       <td>%cm%</td>       <td>%cm%</td>@@ -569,4 +567,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>       <td>%cm%</td>       <td>%cm%</td>@@ -576,29 +576,33 @@     <tr>       <td>`openai-gpt-5`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td>\*</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>     </tr>     <tr>       <td>`openai-gpt-5-mini`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td>\*</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -606,14 +610,16 @@     <tr>       <td>`openai-gpt-5-nano`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td>\*</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -629,4 +635,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>       <td>%cm%</td>       <td>%cm%</td>@@ -648,4 +656,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -661,4 +671,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -676,4 +688,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -689,4 +703,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>       <td>%cm%</td>       <td>%cm%</td>@@ -708,4 +724,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -718,5 +736,7 @@       <td></td>       <td></td>-      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -738,4 +758,6 @@       <td></td>       <td></td>+      <td></td>+      <td></td>     </tr>     <tr>@@ -751,4 +773,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -759,4 +783,6 @@       <td>%cm%</td>       <td>%cm%</td>+      <td></td>+      <td></td>       <td></td>       <td></td> 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -147,17 +147,18 @@    <colgroup>-    <col style={{width: "28.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />-    <col style={{width: "6.0%"}} />+    <col style={{width: "28.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />+    <col style={{width: "5.5%"}} />   </colgroup>   <thead>@@ -171,4 +172,5 @@       <th>AWS EU (Cross-Region)</th>       <th>AWS APJ (Cross-Region)</th>+      <th>AWS JP (Cross-Region)</th>       <th>AWS AU (Cross-Region)</th>       <th>Azure US (Cross-Region)</th>@@ -193,4 +195,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -202,6 +205,7 @@       <td></td>       <td>%cm%</td>-      <td></td>-      <td></td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -223,4 +227,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -238,4 +243,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -253,4 +259,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -264,4 +271,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -277,4 +285,5 @@       <td></td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -294,4 +303,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -313,4 +323,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -324,4 +335,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -336,4 +348,5 @@       <td></td>       <td></td>+      <td>%cm%</td>       <td>%cm%</td>       <td>%cm%</td>@@ -358,4 +371,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -373,4 +387,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -385,4 +400,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -400,4 +416,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -415,4 +432,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -429,4 +447,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -444,4 +463,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -451,30 +471,32 @@     <tr>       <td>`openai-gpt-5.4-mini`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td></td>-      <td>\*</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>       <td></td>     </tr>     <tr>       <td>`openai-gpt-5.4-nano`</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td></td>-      <td>\*</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>       <td></td>     </tr>@@ -489,4 +511,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -504,4 +527,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -519,4 +543,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -534,4 +559,5 @@       <td></td>       <td></td>+      <td></td>       <td>%cm%</td>       <td></td>@@ -548,5 +574,6 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td>%cm%</td>       <td></td>@@ -563,4 +590,5 @@       <td></td>       <td>\*</td>+      <td>\*</td>       <td></td>       <td></td>@@ -578,5 +606,6 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td>%cm%</td>       <td></td>@@ -593,11 +622,13 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>-      <td>%cm%</td>-      <td></td>-      <td>%cm%</td>-      <td></td>-    </tr>-    <tr>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>+      <td></td>+    </tr>+    <tr>+      <td></td>       <td></td>       <td></td>@@ -628,4 +659,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -638,5 +670,6 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>       <td>%cm%</td>       <td></td>@@ -654,4 +687,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -669,4 +703,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -684,4 +719,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -699,4 +735,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -718,4 +755,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -729,4 +767,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -743,11 +782,13 @@       <td>%cm%</td>       <td>%cm%</td>-      <td></td>-      <td>%cm%</td>-      <td></td>-      <td>%cm%</td>-      <td></td>-    </tr>-    <tr>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td>%cm%</td>+      <td></td>+    </tr>+    <tr>+      <td></td>       <td></td>       <td></td>@@ -773,4 +814,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -793,4 +835,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -805,4 +848,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -818,4 +862,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -838,4 +883,5 @@       <td></td>       <td></td>+      <td></td>     </tr>     <tr>@@ -848,4 +894,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -863,4 +910,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -878,4 +926,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td>%cm%</td>@@ -894,4 +943,5 @@       <td>%cm%</td>       <td>%cm%</td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -911... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-monitor+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-monitor@@ -7,16 +7,16 @@ This feature is not available in the People's Republic of China. -Use this topic for Cortex Agents deployed through Snowflake Intelligence or the Agent API. Monitoring shows **live** conversation history and execution traces: planning, tool calls, responses, and user feedback.+Use this topic for Cortex Agents deployed through Snowflake Intelligence or the Agent API. Observability shows **live** conversation history and execution traces: planning, tool calls, responses, and user feedback.  For **batch test runs** and GPA-style metrics, see [](/user-guide/snowflake-cortex/cortex-agents-evaluations). For **custom AI applications** (agents, RAG pipelines, AI workflows on Snowflake compute or other hosts) observed with TruLens, see [](/user-guide/snowflake-cortex/ai-observability/trace-applications-trulens). -## Monitoring vs evaluations (Cortex Agents)+## Observability vs evaluations (Cortex Agents) -The following table compares live monitoring with batch evaluations for Cortex Agents:+The following table compares live observability with batch evaluations for Cortex Agents: -|               | **Monitoring** (this topic)                              | **Evaluations**                                             |+|               | **Observability** (this topic)                           | **Evaluations**                                             | | ------------- | -------------------------------------------------------- | ----------------------------------------------------------- | | Purpose       | Debug and audit **production** conversations and threads | Score the agent on a **dataset** before or after deployment |-| Snowsight     | Agent → **Monitoring** tab                               | Agent → **Evaluations** tab                                 |+| Snowsight     | Agent → **Observability** tab                            | Agent → **Evaluations** tab                                 | | Typical use   | Trace planning, tools, latency, feedback on real queries | Answer correctness, logical consistency, custom LLM judges  | | Documentation | This topic                                               | [](/user-guide/snowflake-cortex/cortex-agents-evaluations)  |@@ -28,11 +28,11 @@ Cortex Agent monitoring uses OpenTelemetry-style event data in `AI_OBSERVABILITY_EVENTS`. The following terms describe how conversations are grouped: -| Term                  | Meaning                                                                                                                                                                                                                                                                    |-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| **Thread**            | A persisted conversation identified by `thread_id`. The **Monitoring** pane lists one row per thread. **Thread length** is the number of turns in that conversation. See [Use threads with the Cortex Agent REST API](/user-guide/snowflake-cortex/cortex-agents-threads). |-| **Turn**              | One user message and the agent's full response for that message (one `agent:run` request). Each turn is a single exchange in a thread.                                                                                                                                     |-| **Trace**             | The OpenTelemetry trace for one turn. All telemetry for that turn shares the same `trace_id` in the `TRACE` column of `AI_OBSERVABILITY_EVENTS`. **One turn = one trace.**                                                                                                 |-| **Span**              | One step inside a trace: LLM planning, a tool call, SQL execution, chart generation, response generation, and so on. **Many spans make up one trace.**                                                                                                                     |-| **Snowflake session** | The platform SQL session context (user, role, warehouse, and related attributes in `RESOURCE_ATTRIBUTES`). A Snowflake session is separate from a conversation thread. One session can include many threads and turns.                                                     |+| Term                  | Meaning                                                                                                                                                                                                                                                                       |+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| **Thread**            | A persisted conversation identified by `thread_id`. The **Observability** pane lists one row per thread. **Thread length** is the number of turns in that conversation. See [Use threads with the Cortex Agent REST API](/user-guide/snowflake-cortex/cortex-agents-threads). |+| **Turn**              | One user message and the agent's full response for that message (one `agent:run` request). Each turn is a single exchange in a thread.                                                                                                                                        |+| **Trace**             | The OpenTelemetry trace for one turn. All telemetry for that turn shares the same `trace_id` in the `TRACE` column of `AI_OBSERVABILITY_EVENTS`. **One turn = one trace.**                                                                                                    |+| **Span**              | One step inside a trace: LLM planning, a tool call, SQL execution, chart generation, response generation, and so on. **Many spans make up one trace.**                                                                                                                        |+| **Snowflake session** | The platform SQL session context (user, role, warehouse, and related attributes in `RESOURCE_ATTRIBUTES`). A Snowflake session is separate from a conversation thread. One session can include many threads and turns.                                                        |  ```text@@ -73,9 +73,26 @@ 2. In the navigation menu, select **AI & ML** %raa% **Agents**. 3. Select the agent whose logs you want to view.-4. Navigate to the **Monitoring** pane of the agent view.+4. Navigate to the **Observability** pane of the agent view. -The **Monitoring** pane lists each conversation thread with its first input, user feedback, thread length, the user who ran it, and when it was last updated. The **Version** column shows the agent configuration version that handled each thread, so you can tell which version of the agent produced a given conversation.+The **Observability** pane lists each conversation thread with its first input, user feedback, thread length, the user who ran it, and when it was last updated. Threads are ordered by when they were last updated. The pane shows threads across every version of the agent. Selecting a specific version in the agent versions panel doesn't filter this pane. Use it to see all usage of an agent in one place. -By default, the **Monitoring** pane loads data as your current role and uses your default warehouse. Use the **Role** and **Warehouse** selectors to override these defaults and query the monitoring data with a specific role and warehouse.+<a id="label-cort... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy@@ -26,5 +26,7 @@   --upload-only   --build-only-  --deploy-only+  --promote-only+  --provision-certs+  --target <target>   --connection <connection>   --host <host>@@ -64,5 +66,5 @@ <dd> -Re-upload source files without rebuilding or redeploying. Only one of `--upload-only`, `--build-only`, or `--deploy-only` can be used at a time. Default: False.+Re-upload source files without rebuilding or redeploying. Only one of `--upload-only`, `--build-only`, or `--promote-only` can be used at a time. Default: False.  </dd>@@ -70,11 +72,23 @@ <dd> -Re-trigger the remote build without re-uploading or redeploying. Only one of `--upload-only`, `--build-only`, or `--deploy-only` can be used at a time. Default: False.--</dd>-<dt>`--deploy-only`</dt>-<dd>--Create or upgrade the Application Service without re-uploading or rebuilding. Only one of `--upload-only`, `--build-only`, or `--deploy-only` can be used at a time. Default: False.+Re-trigger the remote build without re-uploading or redeploying. Only one of `--upload-only`, `--build-only`, or `--promote-only` can be used at a time. Default: False.++</dd>+<dt>`--promote-only`</dt>+<dd>++Create or upgrade the Application Service without re-uploading or rebuilding. Only one of `--upload-only`, `--build-only`, or `--promote-only` can be used at a time. Default: False.++</dd>+<dt>`--provision-certs`</dt>+<dd>++(Snowflake App Runtime only) When deploying a CNG (serverless) app whose account has no per-account URL certificate yet, trigger certificate provisioning automatically instead of only printing the system-function command. Provisioning is asynchronous (up to ~3 hours); the deploy still stops so it can be re-run once provisioning completes. Default: False.++</dd>+<dt><code className="samp">--target <em>TEXT</em></code></dt>+<dd>++(Snowflake App Runtime only) Name of the target (environment) to deploy, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.  </dd>@@ -268,5 +282,5 @@ - `snow app deploy --upload-only`: Re-upload source files without rebuilding or redeploying. - `snow app deploy --build-only`: Re-trigger the build without re-uploading or redeploying.-- `snow app deploy --deploy-only`: Create or upgrade the service without re-uploading or rebuilding.+- `snow app deploy --promote-only`: Create or upgrade the service without re-uploading or rebuilding.  Only one phase flag can be used at a time.@@ -274,5 +288,5 @@ `snow app deploy` is not idempotent. Running it again restarts the selected phase sequence. If upload and build have already succeeded, use-`--deploy-only` instead of rerunning the full pipeline.+`--promote-only` instead of rerunning the full pipeline.  For operating and debugging after deployment: 

--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2026@@ -12,4 +12,29 @@  See [](/developer-guide/snowflake-cli/index) for documentation.++## Version 3.25.0 (Aug 24, 2026)++### New additions++- `snow connection add` now supports `--client-store-temporary-credential`, which writes `client_store_temporary_credential = true` to the new connection in `config.toml`.+- `snow sql --local-only` default can now be set via the `SNOWFLAKE_CLI_SQL_LOCAL_ONLY` environment variable. When unset, the default remains `false`.+- `snow app events` now accepts `--instance ` (Snowflake App Runtime only) to retrieve live container logs from a specific service instance. Useful when horizontal scaling is active and more than one instance is running. Defaults to instance 0 when the flag is omitted.+- The `snow app` commands now support an `app.yml` (version 2) for Snowflake App Runtime projects; when present it drives the flow instead of `snowflake.yml` (the Native App flow is unchanged). Its `targets` block declares named per-environment deployments, and a new `--target` flag on `deploy`, `open`, `events`, `teardown`, and `validate` selects which one to use. `snow app deploy` runs an upload, build, and deploy pipeline, in that order, that can be limited to a single phase with `--upload-only`, `--build-only`, or `--promote-only`.+- `dbt_projects_profiles.yml` support in `snow dbt deploy` is now generally available. When the profiles directory contains a `dbt_projects_profiles.yml`, it takes precedence over `profiles.yml` and is staged into the deployed project under its own name. The profiles directory is the one given by `--profiles-dir`, or the project root when that option is omitted, so projects that already contain a `dbt_projects_profiles.yml` alongside `profiles.yml` will now deploy with the former and emit a warning.++### Fixes and improvements++- A `snow app` command no longer fails because it could not clean up after itself. If a leftover file cannot be deleted (common on Windows, where an editor or antivirus can be holding it), the command still succeeds and warns which directory was left behind. When the bundle directory cannot be cleared before bundling, the command now stops with an explanation of what to do instead of a permissions error.+- `snow app` commands no longer delete anything in a Snowflake App Runtime project's `output` directory apart from the bundle they created there. A project that keeps its own build results, exports or notebook output under `output` lost them to a command that only meant to bundle.+- `snow app events` for Snowflake App Runtime projects can now return more events by requesting a higher `--last` value.+- `snow app deploy` with workspace-backed storage now builds from `versions/live/` (the current working state) instead of the last committed version. In the Workspaces editor, files auto-save to the live version continuously; reading `versions/last` during the build phase caused stale content to be deployed when running from a live workspace session.+- DCM projects: the `snow dcm preview`, `snow dcm refresh`, and `snow dcm test` commands are not yet generally available. They are now hidden from `--help` unless the `enable_dcm_preview_features` CLI feature flag is enabled, so they no longer appear in `snow dcm --help` without an explicit opt-in.+- `snow dcm plan` now tracks the server's own progress, like `snow dcm deploy` already does: its `RENDER`, `COMPILE` and `PLAN` steps advance as the backend reports each phase. Previously `RENDER` and `COMPILE` completed instantly and the rest of the run showed as a single `PLAN` spinner.+- `snow dcm deploy`, `snow dcm plan` and `snow dcm purge` no longer require an active warehouse. Progress tracking read the result with `RESULT_SCAN`, which requires a warehouse.+- `snow dcm deploy`, `snow dcm plan` and `snow dcm purge` now wrap a change line too wide for the terminal, with its continuation aligned under the change instead of breaking back to the left margin. The file list shown while uploading uses the same tree guides as the changeset.+- `snow streamlit deploy --replace`: fixed a crash when replacing a legacy `ROOT_LOCATION` Streamlit app with a versioned deployment.+- Upgraded `GitPython` from 3.1.57 to 3.1.58.+- Upgraded the Python interpreter embedded in Linux binaries from 3.10.16 to 3.10.21.+- Upgraded pip from 26.1.2 to 26.2.1.  ## Version 3.24.1 (Aug 06, 2026) 

--- ahttps://docs.snowflake.com/en/release-notes/2026/10_30+++ bhttps://docs.snowflake.com/en/release-notes/2026/10_30@@ -11,5 +11,5 @@ <a id="about-listing-consumers"></a> -# 10.30 Release Notes (Preview)+# 10.30 Release Notes (no announcements) (Preview)  Content on this page is available in advance of the completion of the 10.30 release, which is currently@@ -21,15 +21,5 @@ For updates to these release notes, see [](#label-rel-notes-change-log-10-30). -## SQL updates--### PERIOD data type (*General availability*)--With this release, Snowflake is pleased to announce the general availability of the PERIOD data type. A PERIOD value-stores an anchored, half-open temporal range `[begin, end)`, with an inclusive beginning bound and an exclusive ending-bound, as a single value. PERIOD values use a DATE, TIME, or TIMESTAMP element type.--Snowflake also provides a family of functions to construct PERIOD values, access their bounds, compare two ranges, and-combine ranges. These functions include `PERIOD_CONSTRUCT`, `PERIOD_BEGIN`, `PERIOD_END`, `PERIOD_OVERLAPS`,-`PERIOD_CONTAINS`, `PERIOD_INTERSECT`, `PERIOD_LDIFF`, and `PERIOD_RDIFF`.+This release contains no significant features, updates, or enhancements to announce.  <a id="label-rel-notes-change-log-10-30"></a>@@ -37,5 +27,10 @@ ## Release notes change log -| Announcement  | Update                        | Date         |-| ------------- | ----------------------------- | ------------ |-| Release notes | Initial publication (preview) | Aug 20, 2026 |+<div className="colwidths-auto">++| Announcement     | Update                                                       | Date         |+| ---------------- | ------------------------------------------------------------ | ------------ |+| Release notes    | Initial publication (preview)                                | Aug 20, 2026 |+| PERIOD data type | **Removed** — feature not enabled in 10.30; will be in 10.31 | Aug 24, 2026 |++</div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-tag+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-tag@@ -11,5 +11,5 @@ <dd> -[](/sql-reference/sql/alter-tag), [](/sql-reference/sql/show-tags), [](/sql-reference/sql/drop-tag), [](/sql-reference/sql/undrop-tag)+[](/sql-reference/sql/alter-tag), [](/sql-reference/sql/show-tags), [](/sql-reference/sql/drop-tag), [](/sql-reference/sql/undrop-tag), [](/user-guide/object-tagging/multi-value-tags)  </dd>@@ -21,6 +21,7 @@ CREATE [ OR REPLACE ] TAG [ IF NOT EXISTS ] <name>     [ ALLOWED_VALUES '<val_1>' [ , '<val_2>' [ , ... ] ] ]+    [ MULTI_VALUE = TRUE ]     [ PROPAGATE = { ON_DEPENDENCY_AND_DATA_MOVEMENT | ON_DEPENDENCY | ON_DATA_MOVEMENT }-      [ ON_CONFLICT = { '<string>' | ALLOWED_VALUES_SEQUENCE } ] ]+      [ ON_CONFLICT = { '<string>' | ALLOWED_VALUES_SEQUENCE | MERGE } ] ]     [ COMMENT = '<string_literal>' ] ```@@ -85,4 +86,14 @@  </dd>+<dt>`MULTI_VALUE = TRUE`</dt>+<dd>++Specifies that the tag can store more than one string value on the same object or column. After you set this property, you+can't unset it or set it to FALSE. To add or remove values on an object, use `ADD VALUE` and `DROP VALUE`. For more+information, see [](/user-guide/object-tagging/multi-value-tags).++Default: The tag stores a single value.++</dd> <dt>`PROPAGATE = { ON_DEPENDENCY_AND_DATA_MOVEMENT | ON_DEPENDENCY | ON_DATA_MOVEMENT }`</dt> <dd>@@ -126,5 +137,5 @@  </dd>-<dt><code className="samp">ON_CONFLICT = &#123; '<em>string</em>' | ALLOWED_VALUES_SEQUENCE &#125;</code></dt>+<dt><code className="samp">ON_CONFLICT = &#123; '<em>string</em>' | ALLOWED_VALUES_SEQUENCE | MERGE &#125;</code></dt> <dd> @@ -167,4 +178,11 @@  If there is a conflict, then the value of `my_tag` will be `blue` because it comes before `red` in the allowed values list.++</dd>+<dt>`MERGE`</dt>+<dd>++Combines conflicting tag values into multiple values on the target object. You can set `ON_CONFLICT = MERGE` only when+`MULTI_VALUE = TRUE`. For more information, see [](/user-guide/object-tagging/multi-value-tags).  </dd> 

--- ahttps://docs.snowflake.com/en/release-notes/preview-features+++ bhttps://docs.snowflake.com/en/release-notes/preview-features@@ -78,4 +78,11 @@   </thead>   <tbody>+    <tr>+      <td>Request Access in Workspaces</td>+      <td>Open</td>+      <td>August 2026</td>+      <td>[](/user-guide/access-requests-workspaces)</td>+      <td>Resolve access-related SQL errors in Workspaces by submitting access requests from %sf-web-interface%. ACCOUNTADMIN and SECURITYADMIN roles review requests on the Requests &amp; Approvals page. Enable per account by setting `FEATURE_ENABLE_REQUEST_ACCESS_FOR_WORKSPACES = 'ENABLED'`.</td>+    </tr>     <tr>       <td>[Cortex Agent code execution tool](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool)</td>@@ -205,4 +212,14 @@     </tr>     <tr>+      <td>Organization Command Center Organization Features</td>+      <td>Open</td>+      <td>August 2026</td>+      <td>[](/user-guide/organization-hub-command-center), [](/user-guide/organization-hub-command-center-features)</td>+      <td>+        From the organization account, see which organization-level capabilities are enabled in Command Center, starting+        with premium views. You can enable or disable premium views through Snowflake Support.+      </td>+    </tr>+    <tr>       <td>Organization Command Center 3rd party access configuration</td>       <td>Open</td>@@ -394,11 +411,4 @@       <td>[](/user-guide/dynamic-tables/custom-incrementalization)</td>       <td>Define custom MERGE or INSERT refresh logic for dynamic tables when standard refresh modes don't support your transformation pattern.</td>-    </tr>-    <tr>-      <td>Catalog integration for Snowflake Postgres</td>-      <td>Open</td>-      <td>April 2026</td>-      <td>[](/user-guide/snowflake-postgres/postgres-pg_lake)</td>-      <td></td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/credit-usage-limit+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/credit-usage-limit@@ -1,6 +1,7 @@-# Cost controls for CoCo+# Daily credit usage limits for CoCo  This feature is not available in the People's Republic of China. +- [Cost controls for CoCo](/user-guide/cortex-code/cost-controls) - [CoCo](/user-guide/cortex-code/cortex-code) - [CoCo Desktop](/user-guide/cortex-code/cortex-code-desktop)@@ -10,4 +11,7 @@ limits help organizations control CoCo consumption by blocking access when a user's estimated credit usage in a rolling 24-hour window exceeds the configured threshold.++For other CoCo spend controls, including budgets and per-user quotas, see+[Cost controls for CoCo](/user-guide/cortex-code/cost-controls).  Credit limits are a separate, complementary mechanism to database role grants. A user needs both a qualifying@@ -47,4 +51,6 @@ </div> +<a id="label-how-credit-limits-work"></a>+ ## How credit limits work @@ -102,4 +108,6 @@ can set these parameters. +<a id="label-coco-cli-limits"></a>+ ## CoCo CLI limits @@ -139,4 +147,6 @@ ``` +<a id="label-coco-desktop-limits"></a>+ ## CoCo Desktop limits @@ -176,4 +186,6 @@ ``` +<a id="label-coco-snowsight-limits"></a>+ ## CoCo in Snowsight limits @@ -212,4 +224,6 @@ ALTER USER jsmith UNSET CORTEX_CODE_SNOWSIGHT_DAILY_EST_CREDIT_LIMIT_PER_USER; ```++<a id="label-when-a-limit-is-reached"></a>  ## When a limit is reached@@ -231,4 +245,6 @@  Administrators can adjust or remove the limit at any time to restore access.++<a id="label-listing-users-with-custom-limits"></a>  ## Listing users with custom limits@@ -272,7 +288,9 @@ You can modify the parameter name in the `SHOW PARAMETERS LIKE` clause to check the Snowsight parameter instead. +<a id="label-configuring-limits-for-your-organization"></a>+ ## Example: Configuring limits for your organization -The following example sets default limits for all users in the account across both surfaces, then assigns a+The following example sets default limits for all users in the account across all three surfaces, then assigns a higher limit to a power user for CLI usage:  

--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-tag+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-tag@@ -9,5 +9,5 @@ <dd> -[](/sql-reference/sql/create-tag), [](/sql-reference/sql/drop-tag), [](/sql-reference/sql/show-tags), [](/sql-reference/sql/undrop-tag)+[](/sql-reference/sql/create-tag), [](/sql-reference/sql/drop-tag), [](/sql-reference/sql/show-tags), [](/sql-reference/sql/undrop-tag), [](/user-guide/object-tagging/multi-value-tags)  </dd>@@ -23,6 +23,7 @@ ALTER TAG [ IF EXISTS ] <name> SET   [ ALLOWED_VALUES '<val_1>' [ , '<val_2>' [ , ... ] ] ]+  [ MULTI_VALUE = TRUE ]   [ PROPAGATE = { ON_DEPENDENCY_AND_DATA_MOVEMENT | ON_DEPENDENCY | ON_DATA_MOVEMENT }-    [ ON_CONFLICT = { '<string>' | ALLOWED_VALUES_SEQUENCE } ] ]+    [ ON_CONFLICT = { '<string>' | ALLOWED_VALUES_SEQUENCE | MERGE } ] ]   [ COMMENT = '<string_literal>' ] @@ -98,4 +99,11 @@  </dd>+<dt>`MULTI_VALUE = TRUE`</dt>+<dd>++Converts the tag so it can store more than one string value on the same object or column. After you set this property, you+can't unset it or set it to FALSE. For more information, see [](/user-guide/object-tagging/multi-value-tags).++</dd> <dt>`PROPAGATE = { ON_DEPENDENCY_AND_DATA_MOVEMENT | ON_DEPENDENCY | ON_DATA_MOVEMENT }`</dt> <dd>@@ -144,5 +152,5 @@  </dd>-<dt><code className="samp">ON_CONFLICT = &#123; '<em>string</em>' | ALLOWED_VALUES_SEQUENCE &#125;</code></dt>+<dt><code className="samp">ON_CONFLICT = &#123; '<em>string</em>' | ALLOWED_VALUES_SEQUENCE | MERGE &#125;</code></dt> <dd> @@ -186,4 +194,11 @@  If there is a conflict, then the value of `my_tag` will be `blue` because it comes before `red` in the allowed values list.++</dd>+<dt>`MERGE`</dt>+<dd>++Combines conflicting tag values into multiple values on the target object. You can set `ON_CONFLICT = MERGE` only when+`MULTI_VALUE = TRUE`. For more information, see [](/user-guide/object-tagging/multi-value-tags).  </dd> 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/ai-observability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/ai-observability@@ -29,5 +29,5 @@ | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **%sf-intelligence%** and **Cortex Agents** | Live agent threads and traces; batch evaluations on a dataset                                              | [](/user-guide/snowflake-cortex/cortex-agents-monitor), [](/user-guide/snowflake-cortex/cortex-agents-evaluations)               |-| **CoCo**                                    | Prompt traces in the event table; credits, tokens, models, and request IDs in Account Usage                | [](/user-guide/cortex-code/cortex-code-snowsight/observability), [](/user-guide/cortex-code/credit-usage-limit)                  |+| **CoCo**                                    | Prompt traces in the event table; credits, tokens, models, and request IDs in Account Usage                | [](/user-guide/cortex-code/observability), [](/user-guide/cortex-code/credit-usage-limit)                                        | | **Cortex Analyst**                          | Request and response logs; batch evaluations                                                               | [](/user-guide/snowflake-cortex/cortex-analyst/admin-observability), [](/user-guide/snowflake-cortex/cortex-analyst-evaluations) | | **Cortex Search**                           | Request logs when logging is enabled; query with `GET_AI_OBSERVABILITY_EVENTS` and `CORTEX SEARCH SERVICE` | [](/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor)                                                             |@@ -43,5 +43,5 @@ ### %sf-intelligence% and Cortex Agents -Cortex Agents deployed through the Agent API or %sf-intelligence% log conversation threads, turns, and execution spans automatically into `SNOWFLAKE.LOCAL.AI_OBSERVABILITY_EVENTS`. Use the **Monitoring** tab or [](/user-guide/snowflake-cortex/cortex-agents-monitor) to debug production conversations. Use the **Evaluations** tab or [](/user-guide/snowflake-cortex/cortex-agents-evaluations) to score an agent on a dataset before or after deployment.+Cortex Agents deployed through the Agent API or %sf-intelligence% log conversation threads, turns, and execution spans automatically into `SNOWFLAKE.LOCAL.AI_OBSERVABILITY_EVENTS`. Use the **Observability** tab or [](/user-guide/snowflake-cortex/cortex-agents-monitor) to debug production conversations. Use the **Evaluations** tab or [](/user-guide/snowflake-cortex/cortex-agents-evaluations) to score an agent on a dataset before or after deployment.  Credit usage appears in [CORTEX_AGENT_USAGE_HISTORY](/sql-reference/account-usage/cortex_agent_usage_history) and [SNOWFLAKE_INTELLIGENCE_USAGE_HISTORY](/sql-reference/account-usage/snowflake_intelligence_usage_history_view). Those views include request IDs, user and agent identifiers, token counts with per-model breakdowns, and a `METADATA` column for interface and role context. Resource and shared budgets are described in [](/user-guide/snowflake-cortex/cortex-agents-resource-budgets) and [](/user-guide/snowflake-cortex/governance-and-availability/ai-cost-management-and-governance).@@ -49,11 +49,13 @@ ### CoCo -CoCo writes span records to `AI_OBSERVABILITY_EVENTS` for each prompt. Snowsight, Desktop, and the CLI record credits, tokens, models, and request IDs in separate Account Usage views.+CoCo writes span records to `AI_OBSERVABILITY_EVENTS` for each prompt. All three CoCo surfaces (Snowsight, Desktop, and the CLI) are traced the same way, emit the same spans, and use the same access model. For what's captured and how to query it, see [](/user-guide/cortex-code/observability). -- **Snowsight**: [Observability](/user-guide/cortex-code/cortex-code-snowsight/observability) and [CORTEX_CODE_SNOWSIGHT_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_snowsight_usage_history)-- **Desktop**: [Audit logging and observability](/user-guide/cortex-code/cortex-code-desktop/security#audit-logging-and-observability) and [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view)-- **CLI**: [CoCo CLI](/user-guide/cortex-code/cortex-code-cli) and [CORTEX_CODE_CLI_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_cli_usage_history)+Credits, tokens, models, and request IDs for every surface are recorded in [SNOWFLAKE_COCO_USAGE_HISTORY](/sql-reference/account-usage/snowflake_coco_usage_history), whose `INTERFACE` column identifies the originating surface. Per-surface views are also available: -See also [credit usage limits](/user-guide/cortex-code/credit-usage-limit).+- **Snowsight**: [CORTEX_CODE_SNOWSIGHT_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_snowsight_usage_history)+- **Desktop**: [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view) (see also [Audit logging and observability](/user-guide/cortex-code/cortex-code-desktop/security#audit-logging-and-observability))+- **CLI**: [CORTEX_CODE_CLI_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_cli_usage_history)++See also [Cost controls for CoCo](/user-guide/cortex-code/cost-controls) and [daily credit usage limits](/user-guide/cortex-code/credit-usage-limit).  ### Cortex Analyst@@ -115,4 +117,6 @@ Credits, tokens, and request metadata (such as model name, request ID, and user ID) for most AI features are recorded in [Account Usage](/sql-reference/account-usage) views. Traces for agents, CoCo, Search, and TruLens are stored separately in `AI_OBSERVABILITY_EVENTS`. Some workloads, such as CoCo, support joining trace data to usage rows on `REQUEST_ID` to attribute cost to individual prompts. +Base spend reporting on the usage views rather than on `AI_OBSERVABILITY_EVENTS`. Trace delivery is best effort, so totals computed from the event table can under-report consumption. For the authoritative sources, see [](/sql-reference/local/ai_observability_events#label-ai-observability-events-billing).+ For usage views, budget types, alerts, and showback patterns by feature, see [AI cost management and governance](/user-guide/snowflake-cortex/governance-and-availability/ai-cost-management-and-governance). For list prices and consumption units, see [Cortex pricing](/user-guide/snowflake-cortex/pricing).  

--- ahttps://docs.snowflake.com/en/user-guide/object-tagging/propagation+++ bhttps://docs.snowflake.com/en/user-guide/object-tagging/propagation@@ -90,6 +90,6 @@ and there is no conflict. -The ON_CONFLICT property of a tag determines what happens when there is a conflict. You have three options for handling tag propagation-conflicts:+The ON_CONFLICT property of a tag determines what happens when there is a conflict. You have the following options for handling tag+propagation conflicts:  - **Option 1:** Replace the value of the tag with the string `CONFLICT`. This is the default if you don't set the ON_CONFLICT parameter@@ -124,4 +124,6 @@   are resolved. For example, if you change the order of the values in the allowed list, then future conflicts could result in a different   value being assigned to the tag.+- **Option 4:** Combine conflicting values into a set of values on the target object. Set `ON_CONFLICT = MERGE`. This option is valid+  only when the tag has `MULTI_VALUE = TRUE`. For more information, see [](/user-guide/object-tagging/multi-value-tags).  To track conflicts associated with tag propagation, see [](#label-tag-propagation-event-table).@@ -157,7 +159,9 @@ | `record_attributes` | `tag_name`        | <code className="samp"><em>tag_name</em></code>                                                      | Name of the tag that had an event during propagation.                                                                                                                         | | `record_attributes` | `event_type`      | `CONFLICT`                                                                                           | Indicates that a conflict occurred when propagating a tag.                                                                                                                    |+| `record_attributes` | `event_type`      | `PROPAGATION_SKIPPED_MANUAL_TAG`                                                                     | Indicates that Snowflake skipped propagation because the target already has a manually applied tag with the same name, and the value of the manually applied tag is retained. | | `record_attributes` | `event_type`      | `TAG_PROPAGATION_LIMIT_EXCEEDED`                                                                     | Indicates that Snowflake didn't propagate a tag because there were more than 10,000 target objects.                                                                           | | `value`             | `conflict_values` | [<code className="samp"><em>tag_value</em></code>, <code className="samp"><em>tag_value</em></code>] | Array of the tag values that were conflicting.                                                                                                                                |-| `value`             | `resolution_type` | `DEFAULT`, `STRING_OVERRIDE`, or `ALLOWED_VALUES_OVERRIDE`                                           | Indicates the action that Snowflake took when a conflict occurred. To understand why the conflict was resolved in a particular way, see [](#label-tag-propagation-conflicts). |+| `value`             | `resolution_type` | `DEFAULT`, `STRING_OVERRIDE`, `ALLOWED_VALUES_SEQUENCE`, or `MERGE`                                  | Indicates the action that Snowflake took when a conflict occurred. To understand why the conflict was resolved in a particular way, see [](#label-tag-propagation-conflicts). |+| `value`             | `resolution_type` | `SAME_VALUE` or `DIFFERENT_VALUE`                                                                    | For `PROPAGATION_SKIPPED_MANUAL_TAG` events, indicates whether the manually applied value matches the value that would have been propagated.                                  | | `value`             | `resolved_values` | <code className="samp"><em>tag_value</em></code>                                                     | Final value of the tag after Snowflake resolved a conflict.                                                                                                                   | @@ -231,5 +235,8 @@ | `CONFLICT`                       | `default`                 | WARN     | |                                  | `string_override`         | INFO     |-|                                  | `allowed_values_override` | INFO     |+|                                  | `allowed_values_sequence` | INFO     |+|                                  | `merge`                   | INFO     |+| `PROPAGATION_SKIPPED_MANUAL_TAG` | `same_value`              | INFO     |+|                                  | `different_value`         | WARN     | | `TAG_PROPAGATION_LIMIT_EXCEEDED` | n/a                       | ERROR    |  

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-versioning+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-versioning@@ -37,4 +37,6 @@ The live version is the mutable, editable state of an agent. You use it during development to iterate on the agent's configuration, instructions, tools, and skills. Each agent can have at most one live version at a time.+In the API, SQL, and version identifiers, that version is `LIVE`. In %sf-web-interface%, the same version is+displayed as `DRAFT`.  You create a live version in one of the following ways:@@ -142,10 +144,10 @@ You can use these shortcuts in the API endpoint and in stage URIs: -| Shortcut  | Description                                  |-| --------- | -------------------------------------------- |-| `LIVE`    | The current live version                     |-| `FIRST`   | The first committed named version            |-| `LAST`    | The most recently committed named version    |-| `DEFAULT` | The version set as the default for the agent |+| Shortcut  | Description                                               |+| --------- | --------------------------------------------------------- |+| `LIVE`    | The current live version (displayed as `DRAFT` in the UI) |+| `FIRST`   | The first committed named version                         |+| `LAST`    | The most recently committed named version                 |+| `DEFAULT` | The version set as the default for the agent              |  Shortcuts are useful for automation scripts and CI/CD pipelines where the exact version number isn't known ahead@@ -269,5 +271,5 @@ ); --- Run the LIVE (draft) version+-- Run the LIVE version (displayed as DRAFT in the UI) SELECT SNOWFLAKE.CORTEX.DATA_AGENT_RUN(   'MY_DB.MY_SCHEMA.MY_AGENT!LIVE', 

--- ahttps://docs.snowflake.com/en/sql-reference/functions-system+++ bhttps://docs.snowflake.com/en/sql-reference/functions-system@@ -228,4 +228,8 @@     </tr>     <tr>+      <td>[](/sql-reference/functions/system_issue_per_account_certificates)</td>+      <td></td>+    </tr>+    <tr>       <td>[](/sql-reference/functions/system_issue_workload_identity_federation_token)</td>       <td></td>@@ -737,5 +741,10 @@     <tr>       <td>[](/sql-reference/functions/system_get_tag)</td>-      <td></td>+      <td>++Returns an error if a [multi-value tag](/user-guide/object-tagging/multi-value-tags) has more than one value assigned. Use+[](/sql-reference/functions/system_tag_value_contains) instead.++</td>     </tr>     <tr>@@ -908,4 +917,8 @@     </tr>     <tr>+      <td>[](/sql-reference/functions/system_tag_value_contains)</td>+      <td></td>+    </tr>+    <tr>       <td>[](/sql-reference/functions/system_task_runtime_info)</td>       <td></td> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/events+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/events@@ -33,4 +33,6 @@   --metric <metric>   --raw+  --instance <instance>+  --target <target>   --package-entity-id <package_entity_id>   --app-entity-id <app_entity_id>@@ -164,4 +166,16 @@  </dd>+<dt><code className="samp">--instance <em>INTEGER</em></code></dt>+<dd>++(Snowflake App Runtime only) Zero-based index of the service instance to retrieve logs from. Only valid with `--type log` and no `--since`/`--until`. Defaults to instance 0.++</dd>+<dt><code className="samp">--target <em>TEXT</em></code></dt>+<dd>++(Snowflake App Runtime only) Name of the target (environment) to query events for, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.++</dd> <dt><code className="samp">--package-entity-id <em>TEXT</em></code></dt> <dd> 

--- ahttps://docs.snowflake.com/en/sql-reference/local/ai_observability_events+++ bhttps://docs.snowflake.com/en/sql-reference/local/ai_observability_events@@ -38,4 +38,15 @@ Ingested rows **can't be modified**. Only administrators with the `SNOWFLAKE.AI_OBSERVABILITY_ADMIN` application role can delete rows for retention management. +<a id="label-ai-observability-events-billing"></a>++`AI_OBSERVABILITY_EVENTS` is built for tracing and debugging individual requests, and telemetry is delivered on a **best-effort** basis, which means a span can occasionally be dropped or arrive late. Token and credit values in a span describe what that span reported, so totals you compute from the event table can come in under actual consumption.++To account for spend or reconcile token counts, use one of the following authoritative sources:++- **[Account Usage](/sql-reference/account-usage) and [Organization Usage](/sql-reference/organization-usage) views** for credits, tokens, and per-model breakdowns. Pick the view for the feature you're billing, such as [CORTEX_AGENT_USAGE_HISTORY](/sql-reference/account-usage/cortex_agent_usage_history) for Cortex Agents, [SNOWFLAKE_COCO_USAGE_HISTORY](/sql-reference/account-usage/snowflake_coco_usage_history) for CoCo, or [CORTEX_AI_FUNCTIONS_USAGE_HISTORY](/sql-reference/account-usage/cortex_ai_functions_usage_history) for built-in AI functions. For the full mapping of features to views, see [](/user-guide/snowflake-cortex/governance-and-availability/ai-cost-management-and-governance).+- **The agent API response**, which returns complete token information and the model used for that request in its `usage.tokens_consumed` field. See [TokensConsumed](/user-guide/snowflake-cortex/cortex-agents-run#label-snowflake-agent-run-tokensconsumed).++Joining trace data to a usage view on `REQUEST_ID` is still a good way to attribute a known cost back to the prompt that caused it. Treat the usage view as the source of truth for the amount, and the event table as the explanation of what happened.+ ## What writes to the table @@ -46,5 +57,5 @@ | **Cortex Agents** (including agents used by %sf-intelligence%) | Automatic logging for Agent API and Snowflake Intelligence conversations (one trace per turn); batch evaluation traces from the Snowsight **Evaluations** tab or `EXECUTE_AI_EVALUATION` (see [Terminology](/user-guide/snowflake-cortex/cortex-agents-monitor#label-cortex-agent-observability-terminology)) | [](/user-guide/snowflake-cortex/cortex-agents-monitor), [](/user-guide/snowflake-cortex/cortex-agents-evaluations) | | **External Agent** (TruLens)                                   | TruLens Python SDK via Snowflake connector                                                                                                                                                                                                                                                                    | [](/user-guide/snowflake-cortex/ai-observability/trace-applications-trulens)                                       |-| **CoCo**                                                       | Automatic span records per prompt (`CodingAgentRun`, `CodingAgent.Step-0`)                                                                                                                                                                                                                                    | [](/user-guide/cortex-code/cortex-code), [](/user-guide/cortex-code/cortex-code-snowsight/observability)           |+| **CoCo**                                                       | Automatic span records per prompt (`CodingAgentRun`, `CodingAgent.Step-0`)                                                                                                                                                                                                                                    | [](/user-guide/cortex-code/cortex-code), [](/user-guide/cortex-code/observability)                                 | | **Cortex Search**                                              | One event row per logged request when [`REQUEST_LOGGING`](/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor#label-cortex-search-request-logging) is enabled                                                                                                                                    | [](/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor)                                               |  

--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/collab-ui-manage+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/collab-ui-manage@@ -101,11 +101,14 @@ 2. Select the **Shared by you** tab. 3. Select **Share Data Offering**.-4. In the dialog, select a **Data Offering ID** from the list of registered data-   offerings in your account.-5. Select the collaborators (analysis runners) who should have access to the data+4. In the dialog, select the **Registry** that holds the data offering. Select **Default**+   for the default account registry.+5. Select a **Data Offering ID** from the list of registered data offerings in your+   account.+6. Select the collaborators (analysis runners) who should have access to the data    offering.-6. Select **Submit Request**.+7. Select **Submit Request**. -The data offering is immediately available to the selected analysis runners.+The request appears on the **Update Requests** tab with a status of **Pending**. Monitor the request until its status+changes to **Completed**, which indicates that the data offering is available to the selected analysis runners.  ### Unlink a data offering 

--- ahttps://docs.snowflake.com/en/user-guide/organization-hub-command-center+++ bhttps://docs.snowflake.com/en/user-guide/organization-hub-command-center@@ -5,4 +5,5 @@ - [Organization Hub](/user-guide/organization-hub) - [Organization Hub Insights](/user-guide/organization-hub-insights)+- [Organization Features](/user-guide/organization-hub-command-center-features) - [Command Center 3rd party access configuration](/user-guide/organization-hub-command-center-third-party) @@ -22,6 +23,9 @@ ## Command Center tiles -The following Command Center tile is in preview:+The following Command Center tiles are in preview: +- [Organization Features](/user-guide/organization-hub-command-center-features): See which organization-level+  capabilities are enabled, starting with premium views. Organizations that have a capacity contract have premium views+  enabled by default. To enable or disable premium views, contact Snowflake Support. - [3rd party access configuration](/user-guide/organization-hub-command-center-third-party): Classify member accounts as   internal or external, set the default tenant type for new accounts, and maintain allowed email domains.@@ -32,4 +36,5 @@ ## Access control requirements -Command Center, including 3rd party access configuration, requires the GLOBALORGADMIN role. ORGANIZATION_USAGE application-roles can open [Insights](/user-guide/organization-hub-insights), but they can't open Command Center yet.+Command Center, including Organization Features and 3rd party access configuration, requires the GLOBALORGADMIN role.+ORGANIZATION_USAGE application roles can open [Insights](/user-guide/organization-hub-insights), but they can't open+Command Center yet. 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code@@ -127,4 +127,5 @@ - [CoCo automations in CLI and Snowsight](/user-guide/cortex-code/cortex-code-automations) - [CoCo changelog](/user-guide/cortex-code/changelog)+- [Observability](/user-guide/cortex-code/observability) - [CoCo Agent SDK](/user-guide/cortex-code-agent-sdk/cortex-code-agent-sdk) - [CoCo CLI Model Context Protocol (MCP) support](/user-guide/cortex-code/cortex-code-mcp)@@ -153,6 +154,6 @@ storage costs) is billed at standard Snowflake on-demand rates, as described in the [Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf). -To set daily credit usage limits for CoCo users, see-[Managing CoCo credit usage limits](/user-guide/cortex-code/credit-usage-limit).+To manage CoCo spend, see+[Cost controls for CoCo](/user-guide/cortex-code/cost-controls).  ### CoCo Desktop billing@@ -171,6 +172,6 @@ storage costs) is billed at standard Snowflake on-demand rates, as described in the [Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf). -To set daily credit usage limits for CoCo users, see-[Managing CoCo credit usage limits](/user-guide/cortex-code/credit-usage-limit).+To manage CoCo spend, see+[Cost controls for CoCo](/user-guide/cortex-code/cost-controls).  ### CoCo in %sf-web-interface% billing 

--- ahttps://docs.snowflake.com/en/user-guide/kafka-connector/index+++ bhttps://docs.snowflake.com/en/user-guide/kafka-connector/index@@ -48,7 +48,9 @@  -  The v4 connector isn't yet available as a native Confluent Cloud connector. On Confluent-  Cloud, install it as a custom plugin connector. Contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support) for the-  Confluent package.+  The Confluent package for v4 is published to [Confluent Hub](https://www.confluent.io/hub/snowflakeinc/snowflake-kafka-connector)+  and the [Snowflake package repository](https://sfc-repo.snowflakecomputing.com/kafka-connector/confluent/java/).++  The v4 connector isn't yet available as a fully managed Confluent Cloud connector. On Confluent+  Cloud, install it as a custom plugin connector using one of these packages.   

--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/collab-ui-join+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/collab-ui-join@@ -25,5 +25,5 @@ ## Review a collaboration -Collaborations that require review before joining appear in the **Pending review**+Collaborations that require review before joining appear in the **Ready to Review** section of the **Invited** tab. @@ -33,5 +33,5 @@ 2. In the navigation menu, select **Data sharing** %raa% **Data clean rooms**. 3. Select the **Invited** tab.-4. In the **Pending review** section, select **Start Review** on the collaboration card.+4. In the **Ready to Review** section, select **Start Review** on the collaboration card.  The review flow lets you examine the collaboration details, including:@@ -48,5 +48,5 @@ ## Join a collaboration -Collaborations that are ready to join appear in the **Ready to join** section of the+Collaborations that are ready to join appear in the **Pending Join** section of the **Invited** tab. Collaborations that you have already reviewed also appear here. @@ -63,5 +63,5 @@ Configure your local settings for the collaboration: -- **Local Collaboration Name**: A name for the collaboration in your account. This+- **Collaboration name**: A name for the collaboration in your account. This   can be different from the collaboration name set by the owner. - Review the collaboration description provided by the owner. 

--- ahttps://docs.snowflake.com/en/user-guide/security-access-control-overview+++ bhttps://docs.snowflake.com/en/user-guide/security-access-control-overview@@ -458,2 +458,10 @@ There is no concept of a "super-user" or "super-role" in Snowflake that can bypass authorization checks. All access requires appropriate access privileges.++<a id="label-access-control-access-requests"></a>++## Access Requests++When a query in Workspaces fails because of missing privileges, users can submit an access request from+%sf-web-interface% for administrator review. For more information, see+[](/user-guide/access-requests-workspaces). 

--- ahttps://docs.snowflake.com/en/user-guide/tutorials/dbt-projects-on-snowflake-ci-cd-tutorial+++ bhttps://docs.snowflake.com/en/user-guide/tutorials/dbt-projects-on-snowflake-ci-cd-tutorial@@ -555,5 +555,5 @@ ### Create your CI workflow file -When running `snow dbt deploy` in your CI/CD workflow, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, add the following environment variable to your workflow file:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If your CI/CD workflow runs `snow dbt deploy` with Snowflake CLI 3.24.x or earlier, add the following environment variable to your workflow file:  ```yaml@@ -562,5 +562,5 @@ ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI by default in all accounts. At that time, you can safely remove this variable from your workflow. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After your workflow upgrades to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  Don't use `--force` in these deploy steps unless you intentionally want to recreate the dbt project object. In `snow dbt deploy`, `--force` runs `CREATE OR REPLACE DBT PROJECT`, which removes all existing versions and run history.@@ -754,5 +754,5 @@ ### Create your CD workflow file -When running `snow dbt deploy` in your CI/CD workflow, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, add the following environment variable to your workflow file:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If your CI/CD workflow runs `snow dbt deploy` with Snowflake CLI 3.24.x or earlier, add the following environment variable to your workflow file:  ```yaml@@ -761,5 +761,5 @@ ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI by default in all accounts. At that time, you can safely remove this variable from your workflow. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After your workflow upgrades to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  Don't use `--force` in these deploy steps unless you intentionally want to recreate the dbt project object. In `snow dbt deploy`, `--force` runs `CREATE OR REPLACE DBT PROJECT`, which removes all existing versions and run history. 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/teardown+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/teardown@@ -16,4 +16,5 @@ snow app teardown   --force+  --target <target>   --connection <connection>   --host <host>@@ -53,4 +54,10 @@  </dd>+<dt><code className="samp">--target <em>TEXT</em></code></dt>+<dd>++(Snowflake App Runtime only) Name of the target (environment) to tear down, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.++</dd> <dt><code className="samp">--connection, -c, --environment <em>TEXT</em></code></dt> <dd> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/connection-commands/add-connection+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/connection-commands/add-connection@@ -33,4 +33,5 @@   --secondary-roles <secondary_roles>   --server-session-keep-alive+  --client-store-temporary-credential   --format <format>   --verbose@@ -166,4 +167,10 @@  Enable server-side session keep-alive to prevent the session from timing out during long operations.++</dd>+<dt>`--client-store-temporary-credential`</dt>+<dd>++Store the temporary credential.  </dd> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate@@ -17,4 +17,5 @@ ```console snow app validate+  --target <target>   --connection <connection>   --host <host>@@ -48,4 +49,10 @@  <dl>+<dt><code className="samp">--target <em>TEXT</em></code></dt>+<dd>++(Snowflake App Runtime only) Name of the target (environment) to validate, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.++</dd> <dt><code className="samp">--connection, -c, --environment <em>TEXT</em></code></dt> <dd> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/open+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/open@@ -18,4 +18,5 @@   --settings   --watch+  --target <target>   --connection <connection>   --host <host>@@ -67,4 +68,10 @@  </dd>+<dt><code className="samp">--target <em>TEXT</em></code></dt>+<dd>++(Snowflake App Runtime only) Name of the target (environment) to open, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.++</dd> <dt><code className="samp">--connection, -c, --environment <em>TEXT</em></code></dt> <dd> 

--- ahttps://docs.snowflake.com/en/user-guide/tables-iceberg-configure-catalog-integration-snowflake-postgres+++ bhttps://docs.snowflake.com/en/user-guide/tables-iceberg-configure-catalog-integration-snowflake-postgres@@ -1,5 +1,3 @@ # Configure a catalog integration for Snowflake Postgres--Available to all accounts.  - [](/user-guide/tables-iceberg)@@ -20,5 +18,5 @@ or manage storage credentials separately. -Snowflake Postgres catalog integrations are currently supported on AWS only.+Snowflake Postgres catalog integrations are currently supported on AWS and Azure only.  ## Prerequisites@@ -43,5 +41,5 @@ - Tables are read-only. Write operations to Postgres-managed Iceberg tables are not supported. - This feature is not supported with burstable Postgres instances.-- This feature is supported on AWS only.+- This feature is supported on AWS and Azure only.  ## Create a catalog integration for Snowflake Postgres 

--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases@@ -78,4 +78,10 @@     <tr>       <td>%snowflake-cli-rn%</td>+      <td>3.25.0</td>+      <td>24-Aug-2026</td>+      <td></td>+    </tr>+    <tr>+      <td>%snowflake-cli-rn%</td>       <td>3.24.1</td>       <td>06-Aug-2026</td> 

--- ahttps://docs.snowflake.com/en/user-guide/organization-hub+++ bhttps://docs.snowflake.com/en/user-guide/organization-hub@@ -12,6 +12,6 @@ - **Insights** (generally available): Monitor and analyze cost, security posture, query health, and storage across all   accounts. See [Organization Hub Insights](/user-guide/organization-hub-insights).-- **Command center** (preview): Configure organization-wide settings, starting with 3rd party access configuration. See-  [Organization Command Center](/user-guide/organization-hub-command-center).+- **Command center** (preview): Configure organization-wide settings, including Organization Features and 3rd party+  access configuration. See [Organization Command Center](/user-guide/organization-hub-command-center).  Organization Hub requires an [organization account](/user-guide/organization-accounts).@@ -37,4 +37,4 @@  Use **Command center** to configure organization-wide settings. Command Center is in preview. For access requirements-and the 3rd party access configuration tile, see+and the Organization Features and 3rd party access configuration tiles, see [Organization Command Center](/user-guide/organization-hub-command-center). 

--- ahttps://docs.snowflake.com/en/user-guide/dynamic-tables/frozen-regions+++ bhttps://docs.snowflake.com/en/user-guide/dynamic-tables/frozen-regions@@ -53,4 +53,9 @@   Rows that fall in both the frozen region and the expired region are still   deleted when the policy runs. For more information, see [](/user-guide/dynamic-tables/storage-lifecycle-policies).+- **Data governance policies on base tables**: If you apply or alter a data governance policy on a+  base table after frozen rows exist, rows in the frozen region keep the values they had+  before the policy was applied or altered. To enforce the policy on frozen rows, apply it directly+  to the dynamic table. For related caveats, see+  [Column-level security considerations](/user-guide/security-column-intro#considerations).  <a id="label-dts-frozen-where-limitations"></a> 

--- ahttps://docs.snowflake.com/en/user-guide/errors-saml+++ bhttps://docs.snowflake.com/en/user-guide/errors-saml@@ -360,6 +360,7 @@ **Authentication fails for a user with email-based mapping even though the user exists.** -The user's email might not be verified. Email-based mapping requires a verified email, and an unverified email fails as an unresolved user-(the generic `390100` error) with no dedicated code to grep for. Verify the user's email, or verify their email domain. See+The user's email might not be verified. Email-based mapping requires a Snowflake verified email, and an unverified email fails as an unresolved user+(the generic `390100` error). Verify the Snowflake user's email, or verify their email domain. For managed+providers, the user must also have a verified email in their Google Workspace or Microsoft tenant. See [](/user-guide/admin-security-fed-auth-oidc#label-oidc-verified-email).  

--- ahttps://docs.snowflake.com/en/user-guide/admin-security-fed-auth-oidc+++ bhttps://docs.snowflake.com/en/user-guide/admin-security-fed-auth-oidc@@ -316,4 +316,9 @@ rules don't apply to `LOGIN_NAME` mapping. +For managed providers, users must also verify their email in their Google Workspace or Microsoft tenant before they can sign in.+Snowflake checks the `email_verified` claim in the ID token; if the email isn't verified at the IdP, login fails. If you include+`'personal'` in `OIDC_ALLOWED_GOOGLE_HOSTED_DOMAINS` or `OIDC_ALLOWED_MSFT_TENANTS`, both providers treat personal and unmanaged+accounts as verified by default.+ - **The matched user's email must be verified.** By default, a user whose email isn't verified can't sign in through email-based OIDC   mapping; the login fails as an unresolved user (the same generic error as any other missed lookup). An email counts as verified in either 

--- ahttps://docs.snowflake.com/en/user-guide/organization-hub-insights+++ bhttps://docs.snowflake.com/en/user-guide/organization-hub-insights@@ -4,4 +4,5 @@ - [Organization Command Center](/user-guide/organization-hub-command-center) - [Premium views in the organization account](/user-guide/organization-accounts-premium-views)+- [Organization Features](/user-guide/organization-hub-command-center-features) - [Cortex Code](/user-guide/cortex-code/cortex-code) @@ -25,4 +26,7 @@  The top of Insights contains highlights from each section. Select a tile to switch to the corresponding tile further down the page.++A tile labeled **Coming soon** is in private preview. To request access, use the feedback button in+%sf-web-interface% or contact your Snowflake account team.  ## Billing and Cost 

--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_issue_per_account_app_service_certificate+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_issue_per_account_app_service_certificate@@ -20,6 +20,6 @@  You currently must run this function in order to change-[ENABLE_PER_ACCOUNT_APP_SERVICE_URL](#label-ENABLE-PER-ACCOUNT-APP-SERVICE-URL) or-[ENABLE_PER_ACCOUNT_APP_SERVICE_PRIVATELINK_URL](#label-ENABLE-PER-ACCOUNT-APP-SERVICE-PRIVATELINK-URL)+[ENABLE_PER_ACCOUNT_APP_SERVICE_URL](/sql-reference/parameters#label-enable-per-account-app-service-url) or+[ENABLE_PER_ACCOUNT_APP_SERVICE_PRIVATELINK_URL](/sql-reference/parameters#label-enable-per-account-app-service-privatelink-url) to true.  

--- ahttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-migrate-from-dbt-core+++ bhttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-migrate-from-dbt-core@@ -452,10 +452,10 @@ If both files are present in the project root, Snowflake uses `dbt_projects_profiles.yml` in Workspaces, Cortex Code Desktop in Snowflake-managed mode, and the dbt project object. If `dbt_projects_profiles.yml` isn't present, Snowflake uses `profiles.yml` as before. -When running `snow dbt deploy`, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, set the following environment variable:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If you're running Snowflake CLI 3.24.x or earlier, set the following environment variable before you run `snow dbt deploy`:  ```bash ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI for all accounts. At that time, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After you upgrade to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  Here's a `dbt_projects_profiles.yml` or `profiles.yml` you can drop in. It defines a `dev` and a `prod` target: 

--- ahttps://docs.snowflake.com/en/user-guide/object-tagging/introduction+++ bhttps://docs.snowflake.com/en/user-guide/object-tagging/introduction@@ -1,4 +1,5 @@ # Introduction to object tagging +- [](/user-guide/object-tagging/multi-value-tags) - [](/user-guide/tag-based-masking-policies) - [Process PII data using Snowflake RBAC, DAC, Row Access Policies, and Column Level Security (Snowflake Quickstart)](https://quickstarts.snowflake.com/guide/getting_started_with_pii/)@@ -10,5 +11,6 @@ A tag is a schema-level object that can be assigned to another Snowflake object. Users associate a tag with an arbitrary string value when assigning the tag to a Snowflake object. Snowflake stores the tag and its string value as a key-value pair. The tag must be unique for-your schema, and the tag value is always a string.+your schema, and the tag value is always a string. To assign more than one string value to the same tag, use+[](/user-guide/object-tagging/multi-value-tags).  The following are general characteristics of object tagging: 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index@@ -54,5 +54,5 @@ Revoking SNOWFLAKE.CORTEX_USER from PUBLIC also removes access to other Covered AI Features, including Cortex AI functions (AI_COMPLETE, AI_TRANSLATE, AI_CLASSIFY, and others). If you-need finer-grained control, use the credit limit parameter in the following section to block+need finer-grained control, use the daily credit usage limit parameter to block Desktop access without affecting other AI features. @@ -60,5 +60,5 @@ Setting the account-level `CORTEX_CODE_DESKTOP_DAILY_EST_CREDIT_LIMIT_PER_USER` parameter to `0` blocks all users, and you can then selectively allow access for individual users by assigning-them a positive value. See [Cost controls for CoCo](/user-guide/cortex-code/credit-usage-limit).+them a positive value. See [Daily credit usage limits for CoCo](/user-guide/cortex-code/credit-usage-limit).  ## What's new 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/governance-and-availability/ai-cost-management-and-governance+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/governance-and-availability/ai-cost-management-and-governance@@ -283,9 +283,9 @@     <tr>       <td>Cortex Code CLI (Consumption)</td>-      <td>[Shared resource budgets](/user-guide/budgets/budget-shared-resources), [credit usage limits](/user-guide/cortex-code/credit-usage-limit)</td>+      <td>[Shared resource budgets](/user-guide/budgets/budget-shared-resources), [daily credit usage limits](/user-guide/cortex-code/credit-usage-limit)</td>     </tr>     <tr>       <td>Cortex Code in Snowsight</td>-      <td>[Shared resource budgets](/user-guide/budgets/budget-shared-resources), [credit usage limits](/user-guide/cortex-code/credit-usage-limit)</td>+      <td>[Shared resource budgets](/user-guide/budgets/budget-shared-resources), [daily credit usage limits](/user-guide/cortex-code/credit-usage-limit)</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-deploy+++ bhttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-deploy@@ -37,10 +37,10 @@ The following examples illustrate how to use the `snow dbt deploy` command: -When running `snow dbt deploy`, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, set the following environment variable:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If you're running Snowflake CLI 3.24.x or earlier, set the following environment variable before you run `snow dbt deploy`:  ```bash ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI for all accounts. At that time, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After you upgrade to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  Don't use `--force` unless you intentionally want to recreate the dbt project object. In `snow dbt deploy`, `--force` runs `CREATE OR REPLACE DBT PROJECT`, which removes all existing versions and run history. 

--- ahttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-environment-variables+++ bhttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-environment-variables@@ -609,10 +609,10 @@ - `--external-access-integration`: Attaches an external access integration to the dbt project object. Required when your project pulls in private Git packages or remote dependencies via `dbt deps`. Pass the flag once per integration. See [Admin setup](#admin-setup). -When running `snow dbt deploy`, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, set the following environment variable:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If you're running Snowflake CLI 3.24.x or earlier, set the following environment variable before you run `snow dbt deploy`:  ```bash ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI for all accounts. At that time, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After you upgrade to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  ```bash 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dbt-commands/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dbt-commands/deploy@@ -366,10 +366,10 @@ ## Usage notes -When running `snow dbt deploy`, if your Snowflake account doesn't yet recognize `dbt_projects_profiles.yml` by default, set the following environment variable:+Snowflake CLI 3.25.0 and later support `dbt_projects_profiles.yml` by default. If you're running Snowflake CLI 3.24.x or earlier, set the following environment variable before you run `snow dbt deploy`:  ```bash ``` -By early September 2026, `dbt_projects_profiles.yml` will be supported in Snowflake CLI for all accounts. At that time, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).+After you upgrade to Snowflake CLI 3.25.0 or later, you can safely remove this variable. For more information, see [Use dbt_projects_profiles.yml for a unified development-to-production experience](/user-guide/data-engineering/dbt-projects-on-snowflake-best-practices#label-dbt-projects-profiles-file).  The `snow dbt deploy` command uploads local files to a temporary stage and either creates a new object or updates an existing dbt project object by making a new version. A valid dbt project object must contain `dbt_project.yml` and one of the supported profile files: