// troubleshooting guide · apache superset
Superset Dashboard Slow or Charts Timing Out
- Status
- Workaround available
- platforms:
- Self-hosted, Preset
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · apache-superset/dashboard-slow-timeout4 FIXES
// quick answer
Superset charts time out when a query runs longer than the 60-second client timeout or the proxy/WSGI timeout. Speed up or cache the queries, then raise SUPERSET_WEBSERVER_TIMEOUT together with your proxy and Gunicorn timeouts.
Most likely fix: Find the slow query
How to fix it
// try these in order, the most common fix is first
FIX 1Find the slow query
- 01Open the chart, click ... > View query
- 02Run it in SQL Lab or directly on the database
- 03If it is slow there too, add indexes, filters or a pre-aggregated table
Did this fix it?FIX 2Turn on caching
- 01Configure DATA_CACHE_CONFIG with Redis in superset_config.py
- 02Set CACHE_DEFAULT_TIMEOUT
- 03Optionally set cache timeouts per dataset or per chart
Did this fix it?FIX 3Raise timeouts at every layer
- 01Set SUPERSET_WEBSERVER_TIMEOUT (e.g. 300) in superset_config.py
- 02Raise nginx proxy_read_timeout and proxy_connect_timeout to at least the same value
- 03Keep the Gunicorn/WSGI timeout less than or equal to SUPERSET_WEBSERVER_TIMEOUT
- 04Restart all services
Did this fix it?FIX 4Split heavy dashboards
- 01Move rarely used charts to a second dashboard or tab
- 02Use native filters with defaults that narrow the date range
Did this fix it?
SANDBOX · apache-superset RUNS IN YOUR BROWSER
Try it: browse a sample shop and watch visitors, funnels and live data arrive
A hands-on Apache Superset-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Charts spin for a long time, show a timeout warning, or the dashboard returns 504 Gateway Timeout.
Why it happens
- C-01Slow queries on large, unaggregated tables
- C-02Too many charts on one dashboard querying at once
- C-03No results caching configured
- C-04SUPERSET_WEBSERVER_TIMEOUT (default 60s) lower than query time
- C-05Nginx/load balancer timeout lower than Superset's
- C-06Undersized web server or database
// this guide also covers
- superset dashboard slow
- superset chart timeout
- superset 504 gateway timeout
- SUPERSET_WEBSERVER_TIMEOUT
- why is superset so slow
Still not working?
If Apache Superset keeps failing, you're not alone. See every Apache Superset problem users report or the alternatives people switch to.
Done fighting Apache Superset? Our small team builds your own Apache Superset 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 →
Metabase Dashboard Slow or Not Loading (Metabase)
Power BI Gateway Offline or Could Not Be Reached (Microsoft Power BI)
Tableau "Unable to Start Due to an Internal Licensing Error" (Tableau)
Looker Studio GA4 Quota Exceeded Error (Looker Studio)
Other Apache Superset errors
- Superset CSRF Session Token Is Missing Error
- Superset Refusing to Start Due to Insecure SECRET_KEY
- Superset Alerts and Reports Not Sending Emails
- Superset Embedded Dashboard Not Loading (403 or Refused to Connect)
- Superset Could Not Load Database Driver
- Superset CSV Upload Option Missing
- Superset Forgot Admin Password (How to Reset Login)
- Superset Dashboards Broken After Upgrade