Improve clarity on freshness checks for views - #9844
Merged
Conversation
Clarify warning message regarding freshness checks for sources that are views. Makes clear that loaded_at_field and loaded_at_query are necessary for views.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the state-aware orchestration documentation to clarify how freshness checks behave for sources that are views, and to emphasize that loaded_at_field or loaded_at_query is required to determine freshness in that case.
Changes:
- Rewords the guidance about freshness checks for sources that are views.
- Adds an explicit instruction to configure
loaded_at_fieldorloaded_at_queryfor view-based sources.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - If a source is a view in the data warehouse, dbt can’t track updates from the warehouse metadata when the view changes. Without a `loaded_at_field` or `loaded_at_query`, dbt treats the source as "always fresh” and emits a warning during freshness checks. To check freshness for sources that are views, add a `loaded_at_field` or `loaded_at_query` to your configuration. | ||
| - If a source is a view in the data warehouse, the available metadata is usually insufficient to discern freshness and dbt will emit a warning during freshness checks. | ||
|
|
||
| To determine fresheness for sources that are views, add a `loaded_at_field` or `loaded_at_query` to your configuration. |
Contributor
There was a problem hiding this comment.
Suggested change
| To determine fresheness for sources that are views, add a `loaded_at_field` or `loaded_at_query` to your configuration. | |
| To determine freshness for sources that are views, add a `loaded_at_field` or `loaded_at_query` to your configuration. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
nataliefiann
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify warning message regarding freshness checks for sources that are views.
Makes clear that loaded_at_field and loaded_at_query are necessary for views.
What are you changing in this pull request and why?
Checklist
🚀 Deployment available! Here are the direct links to the updated files: