// troubleshooting guide · metabase
Metabase 'Your Question Took Too Long' Error
- Status
- Workaround available
- platforms:
- Metabase Cloud, self-hosted
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · metabase/question-took-too-long5 FIXES
// quick answer
This error usually means something between Metabase and the database cut the request, very often a load balancer or Nginx proxy with a 60-second timeout. Raise the proxy timeout, then speed up the query itself.
Most likely fix: Check the proxy or load balancer timeout
How to fix it
// try these in order, the most common fix is first
FIX 1Check the proxy or load balancer timeout
- 01If the error appears at exactly 60 seconds, look at your load balancer idle timeout
- 02For Nginx, raise proxy_read_timeout in the Metabase server block and reload Nginx
- 03Check the browser Network tab to see which layer returned the error
Did this fix it?FIX 2Check the database timeout
- 01Ask your DBA whether the database or the Metabase user has a statement timeout
- 02Raise it for the Metabase user if appropriate
Did this fix it?FIX 3Raise Metabase's query timeout (self-hosted)
- 01Set the MB_DB_QUERY_TIMEOUT_MINUTES environment variable
- 02Restart Metabase
Did this fix it?FIX 4Compare with the database directly
- 01Run the same SQL in your database client
- 02If it is just as slow, optimize the query, add indexes or pre-aggregate
- 03If it is much faster outside Metabase, review your Metabase deployment and resources
Did this fix it?FIX 5Fix column types
- 01Store dates and numbers in native types instead of text
- 02Avoid casts in filters on large tables
Did this fix it?
SANDBOX · metabase RUNS IN YOUR BROWSER
Try it: browse a sample shop and watch visitors, funnels and live data arrive
A hands-on Metabase-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
A question or dashboard card shows 'Your question took too long', often after exactly 60 seconds or a few minutes.
Why it happens
- C-01Load balancer idle timeout (for example AWS ELB at 60 seconds)
- C-02Reverse proxy (Nginx) read timeout
- C-03Database or session statement timeout
- C-04Query scanning too much data
- C-05Columns stored as the wrong type forcing on-the-fly conversions
// this guide also covers
- your question took too long metabase
- metabase query timeout
- metabase timeout 60 seconds
- metabase query timed out
Still not working?
If Metabase keeps failing, you're not alone. See every Metabase problem users report or the alternatives people switch to.
Done fighting Metabase? Our small team builds your own Metabase alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Superset Dashboard Slow or Charts Timing Out (Apache Superset)
Power BI Gateway Offline or Could Not Be Reached (Microsoft Power BI)
Looker Studio GA4 Quota Exceeded Error (Looker Studio)
Tableau "Unable to Start Due to an Internal Licensing Error" (Tableau)
PostHog Toolbar or Heatmaps Not Loading (PostHog)
Other Metabase errors
- Metabase Dashboard Slow or Not Loading
- Metabase Not Syncing New Tables or Columns
- Metabase Filter Dropdown Not Showing Values
- Metabase Linked Filters Not Working
- Metabase Not Sending Emails or Alerts
- Metabase Can't Connect to Database
- Metabase Tables Not Showing
- Metabase Dates and Times Wrong (Timezone Off)