From 7dea0900dd5c0a94af277eac37bb97da163feffc Mon Sep 17 00:00:00 2001 From: Cameron Afzal Date: Mon, 12 Feb 2024 08:12:00 -0800 Subject: [PATCH] Correct state requirement / caveat for clarity --- website/docs/docs/dbt-cloud-apis/project-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-cloud-apis/project-state.md b/website/docs/docs/dbt-cloud-apis/project-state.md index 62136b35463..78dff4309db 100644 --- a/website/docs/docs/dbt-cloud-apis/project-state.md +++ b/website/docs/docs/dbt-cloud-apis/project-state.md @@ -81,5 +81,5 @@ Here are some limitations of the state representation in the Discovery API: - Users must access the default production environment to know the latest state of a project. - The API gets the definition from the latest manifest generated in a given deployment environment, but that often won’t reflect the latest project code state. - Compiled code results may be outdated depending on dbt Cloud run step order and failures. -- Catalog info can be outdated, or incomplete (in the applied state), based on if/when docs were last generated. +- Catalog info can be outdated, or incomplete (in the applied state), based on if/when `docs generate` was last run. - Source freshness checks can be out of date (in the applied state) depending on when the command was last run, and it’s not included in `build`.