Troubleshooting models
What kind of problem are you having with your model?
Can’t create a model
If you don’t see the model button (three squares):
- Check if you’re using a Metabase version that’s 0.42.0 or greater by going to the top right of the screen and clicking on the gear icon > About Metabase.
- Clear your browser cache.
- Ask your Metabase admin to clear the proxy cache (if you’re using one).
Can’t edit or save changes to a model
If your changes to a model’s metadata or underlying question aren’t showing up:
- Refresh your browser to confirm you’re not viewing cached results.
- Search for known model issues using the label
Querying/Models
. For more information, go to How to find a known bug or limitation.
Model performance is poor
-
Use model persistence.
- Metabase can write back to your data warehouse. If you enable model persistence, Metabase will read a pre-computed and materialized version of the model directly from the database instead of running the query from scratch. Please consider this option is only available in some supported data warehouses.
-
Optimize the underlying saved question or SQL query.
- Ask for less data.
- For models that use SQL questions, look for bottlenecks using SQL EXPLAIN.
-
Optimize your database schemas.
-
Optimize your data warehouse(s) or database(s).
Explanation
Models are a type of saved question, so they will only perform as fast as the original question or SQL query.
If you want to improve the performance of a model, you can make optimizations at the query, schema, or database level (depending on your data permissions, technical expertise, and willingness to tinker).
Are you still stuck?
If you can’t solve your problem using the troubleshooting guides:
- Search or ask the Metabase community.
- Search for known model issues using the label
Querying/Models
. For more information, go to How to find a known bug or limitation.
Read docs for other versions of Metabase.