After experimenting I am quite sure that it is related to celery. The celery worker is somehow not reading the config(maybe also worth to mention in the superset docs that celery requires an own config. I assumed a long time that it doesn't).\n I even tried to spawn the worker with the required arguments via cli, but even that seems not work\n``` celery worker --app=superset.tasks.celery_app:app --pool=prefork -O fair -c 4 -b "<redis://localhost:6379/0>" --result-backend "<redis://localhost:6379/0>" --include superset.sql_lab,superset.tasks -l debug```\nAny help regarding superset+celery in a venv is very welcome as I run out of options to try :smile: