<@UFG3USN8K> I tried the settings above but the cache seems not to be used by the celery worker. (If I disable the sync setting in the frontend the query runs through, otherwise never finish and is according to the hive logs also never send)\n\nMy current config is <https://gist.github.com/0xBADBAC0N/571dcdfc67a747a430116404df5521d2> (maybe you also see something else what is wrong?)\n\nI started superset via\n```export SUPERSET_CONFIG_PATH=/etc/superset/config.py\n. /opt/venvs/apache-superset/bin/activate\n(apache-superset) root@aw-superset:~# /opt/venvs/apache-superset/bin/superset run -p 8088 --with-threads --reload --debugger```\nAs I was not sure if Superset has its own celery workers I tried also with this additionally:\n```. /opt/venvs/apache-superset/bin/activate\n(apache-superset) root@aw-superset:~# celery worker --app=superset.tasks.celery_app:app --pool=prefork -O fair -c 4```\nThe issue here is that the celery worker returns that is uses sqlite as backend and not the redis one in the config\n``` -------------- celery@aw-superset.analytics.ig.local v4.4.6 (cliffs)\n--- ***** ----- \n-- ******* ---- Linux-5.4.0-0.bpo.3-amd64-x86_64-with-debian-10.4 2020-07-09 21:52:45\n- *** --- * --- \n- ** ---------- [config]\n- ** ---------- .&gt; app:         __main__:0x7f13190d9780\n- ** ---------- .&gt; transport:   sqla+sqlite:///celerydb.sqlite\n- ** ---------- .&gt; results:     sqlite:///celery_results.sqlite\n- *** --- * --- .&gt; concurrency: 4 (prefork)\n-- ******* ---- .&gt; task events: OFF (enable -E to monitor tasks in this worker)\n--- ***** ----- \n -------------- [queues]\n                .&gt; celery           exchange=celery(direct) key=celery```