Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct state requirement / caveat for clarity #4894

Merged
merged 1 commit into from
Feb 12, 2024
Merged

Correct state requirement / caveat for clarity #4894

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/docs/dbt-cloud-apis/project-state.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Loading