In my case: updating the both ```` SUPERSET_WEBSERVER_TIMEOUTandGUNICORN_TIMEOUT ```` helped me, even though in superset frontend this is showing query timeout actually it is gunicorn timeout, after restarting your superset and check gunicorn process whether is it really running with increased timout amount