auditing-warehouse-view-health

Run a view health audit that calls the data-health-issues endpoint and filters results to the materialized_view type. Each failing entry includes the view name, error message, failure timestamp, and a URL for investigation.

Request a broader audit that uses view-list to check materialized views against their last-queried timestamps. Views that are materialized but not queried recently are surfaced as cleanup candidates you can unmaterialize.

Materialized view failures are usually self-contained HogQL problems such as syntax errors, missing table references, or type mismatches in the view definition. They are typically independent of source or sync health, and view-run-history shows the failure trail.

No, source and external data sync issues are handled by the auditing-warehouse-source-health skill, even though they share the same data-health endpoint. Batch export destinations and transformations belong to other products and are routed rather than diagnosed.

No, the audit is strictly read-only and never calls destructive tools like view-unmaterialize or view-delete on its own. Any fix or unmaterialization requires explicit user confirmation after the report is presented.