Looker content validation found broken dashboard: field removed error how to fix

TL;DR

Work the Content Validator list item by item. For each broken element either restore the removed field in the view with its original name, which repairs every dashboard at once, or edit the element to the replacement field if the removal was deliberate. Revalidate after each fix so the list shrinks to zero, then clear the dashboard cache and confirm as a viewer.

Looker content validation found broken dashboard: field removed error how to fix

Use this when

• The Content Validator lists dashboards with field removed or field not found errors.
• A LookML cleanup removed or renamed fields and dashboards broke afterwards.
• Several dashboards broke on the same field at the same time.

Not for this skill when

• The validator is clean but a dashboard shows no data. That is a data or filter issue, not a removed field.
• The model itself fails LookML validation. Fix the model errors before content validation is meaningful.

Steps

1. Run the Content Validator and export or note every broken element for the dashboard, grouped by missing field. Verify: each group names one field and the elements that use it
2. Check the project history for the field to learn whether it was renamed, merged, or deliberately removed. Verify: the history shows the change and its replacement field if one exists
3. For an accidental removal, restore the field definition in the view with its original name and deploy. Verify: the validator stops listing every element that used that field
4. For a deliberate removal, edit each affected element to the replacement field, checking pivots, filters and table calculations that referenced it. Verify: each edited element runs in the explore without an error
5. Rerun the Content Validator until the dashboard no longer appears in the broken list. Verify: the dashboard has zero validation errors in the report
6. Clear the dashboard cache and open it as a viewer to confirm the repaired tiles render data. Verify: all tiles show results and no error banner remains

Why it happens

Content validation exists because model changes and saved content evolve at different speeds. The cheapest moment to catch a breaking removal is in the same change that removes the field, by running the validator before merging. Teams that gate LookML pull requests on a clean content validation pass turn this class of outage into a review comment.

Looker content validation scans saved dashboards and looks against the current model and reports elements whose fields no longer resolve. A field removal that passed LookML validation still breaks content, because the validator for the model cannot see dashboard references. Deliberate cleanups and accidental deletions look identical in the report, so the fix decision, restore versus repoint, is made per field with the modelling team.

Field notes for Looker specifically. The Admin area holds the diagnostic pages that matter here, System Activity for query history and runtimes, the PDT activity page for derived table builds, and the Content Validator under the content management tools. Keep the browser on the same Looker version as the instance when testing, because explore behaviour and error wording shift slightly between monthly releases. Screenshots from viewers are worth collecting with the exact load time, since Looker support and your own history search both work far better from a timestamp than from a description of slowness.

A practical habit for Looker teams is to keep one test user per permission tier and to test every model change as the most restricted tier, not as an admin. Admins bypass access filters, see every field, and hit warm caches, so admin testing systematically hides the failures viewers get. Pair that with a standing explore that lists the twenty slowest tiles across the instance each week, and most dashboard incidents become follow ups on a report the team already reads, instead of surprises reported by executives in a meeting.

Variants and edge cases

Looker content validator field removed dashboard fix

The validator phrasing matching the report wording.

Looker dashboard broken after field deleted restore or repoint

The decision variant between restoring and repointing.

LookML cleanup broke dashboards content validation list

The cleanup-triggered variant for deliberate refactors.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_UicMjQK20ZEnEeRn4u1CwQ