Looker dashboard tile shows error instead of results: liquid template error fix

TL;DR

Correct the Liquid in the model first, because the tile error is the generated SQL failing on a bad template expansion. Find the field, html parameter, link or filter that uses Liquid, fix the variable name, filter syntax or conditional block, deploy, and reload the tile. Liquid errors often name the tile symptom while the faulty text sits in a view or dashboard filter definition.

Looker dashboard tile shows error instead of results: liquid template error fix

Use this when

• A tile errors after a LookML change that touched Liquid in a field, link or filter.
• The error changes or disappears when dashboard filter values change.
• The same explore runs when the Liquid-using field is removed.

Not for this skill when

• The tile times out with no recent model change. Treat that as a performance issue instead.
• Every tile on the dashboard errors at once. Check the model deploy or connection before Liquid.

Steps

1. Reproduce the tile error and copy the full error text, then remove fields from the tile one at a time to find the Liquid-using element. Verify: the tile runs when the suspect element is removed and fails when it returns
2. Open the element definition in the LookML project and read its Liquid carefully for misspelled variables, unbalanced tags and wrong filter names. Verify: you can point at the exact line whose expansion is invalid
3. Fix the Liquid, using the documented variable form for the context, such as the value variable in an html parameter or the correct templated filter tag in a sql parameter. Verify: the LookML Validator passes on the project
4. Deploy the change and run the tile in the explore with the same dashboard filter values that failed. Verify: the tile returns rows and any link or formatted output renders as intended
5. Check other fields that share the same Liquid pattern, since authors often copy the block between views. Verify: a project search for the faulty pattern returns no remaining copies
6. Reload the dashboard as a viewer and confirm the tile renders, then clear the dashboard cache so other viewers get the fixed version. Verify: the tile shows data with no error banner

Why it happens

Liquid fails at expansion time, which is at tile run time with real values, so static checks miss many faults. The gap between the edit location in a view file and the symptom on a dashboard tile makes these errors feel random until the remove-one-field test isolates the element. Keeping Liquid blocks small and testing them in the explore before publishing the dashboard keeps the fault radius to one field.

Looker uses Liquid in dimension html parameters, links, conditional formatting helpers and templated filters. A mistyped variable such as a misspelled field reference, an unbalanced conditional tag, or a filter tag applied to the wrong type expands into invalid SQL or an invalid render, and the dashboard reports a tile error with little context. The LookML Validator catches some cases, but many Liquid faults only appear when the tile actually runs with real filter values.

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 tile error Liquid template field html fix

The html-parameter variant common in formatted dimensions.

Looker templated filter Liquid syntax error dashboard

The templated filter variant driven by dashboard filter values.

LookML Liquid link parameter broken tile error

The drill-link variant where the link definition carries the fault.

Provenance

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

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

Thread query: Looker dashboard tile shows error instead of results: liquid template error fix

TL;DR: Correct the Liquid in the model first, because the tile error is the generated SQL failing on a bad template expansion. Find the field, html parameter, link or filter that uses Liquid, fix the variable name, filter syntax or conditional block, deploy, and reload the tile. Liquid errors often name the tile symptom while the faulty text sits in a view or dashboard filter definition.