dosubot[bot] commented on issue #38216: URL: https://github.com/apache/superset/issues/38216#issuecomment-3951148647
<!-- Greeting --> Hi @adayush! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> The most common cause of scheduled reports not triggering with no log entries in Docker deployments is **configuration file placement**. In Docker Compose environments, [Superset only loads custom configuration from `docker/pythonpath_dev/superset_config_docker.py`](https://github.com/apache/superset/issues/37357) — if your config is elsewhere, all custom settings including `ALERT_REPORTS`, Celery configuration, and SMTP settings are ignored. **Quick checks:** 1. **Verify your config is being loaded** — check container logs for: ``` Loaded your Docker configuration at [docker/pythonpath_dev/superset_config_docker.py] ``` If you see "Loaded your LOCAL configuration" instead, that's the problem. 2. **Check Celery beat/worker logs** for `reports.scheduler` tasks. If these don't appear, the scheduler isn't running at all. 3. **Verify feature flags aren't being overridden** by environment variables: ```bash docker exec <container> python -c "from superset import app; print(app.config['ALERT_REPORTS'])" docker exec <container> python -c "from superset import app; print(app.config['ALERT_REPORTS_NOTIFICATION_DRY_RUN'])" ``` 4. **Try "Run Now"** on the report from the UI — if that works, the issue is scheduling rather than execution. 5. **Check if the report is stuck in WORKING state** from a previous run. [Reports can get stuck](https://github.com/apache/superset/discussions/34121) if Celery workers became unhealthy. Restarting workers can clear this. Since your 9am reports worked, also verify: - The 4pm report is still marked as `active` in the database - The crontab expression is correct - [Timezone settings are consistent](https://github.com/apache/superset/issues/26962) — try setting `TZ=UTC` in your Docker environment and keeping your report timezone as UTC <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8b00314e-8fd5-45f7-9107-1b95a8b26779?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20most%20common%20cause%20of%20scheduled%20reports%20not%20triggering%20with%20no%20log%20entries%20in%20Docker%20deployments%20is%20%2A%2Aconfiguration%20file%20placement%2A%2A.%20In%20Docker%20Compose%20environments%2C%20%5BSuperset%20only%20loads%20custom%20configuration%20from%20%60docker/pythonpath_dev/superset_config_docker.py%60%5D%28https%3A//github.com/apache/superset/issues/37357%29%20%E2%80%94%20if%20your%20config%20is%20elsewhere%2C%20all%20custom%20settings%20including%20%60ALERT_REPORTS%60%2C%20Celery%20configuration%2C%20and%20SMTP%20settings%20are%20ignored.%0A%0A%2A%2AQuick%20checks%3A%2A%2A%0A%0A1.%20%2A%2AVerify%20your%20config%20is%20being%20loaded%2A%2A%20%E2%80%94%20check%20container%20logs%20for%3A%0A%20%20%20%60%60%60%0A %20%20%20Loaded%20your%20Docker%20configuration%20at%20%5Bdocker/pythonpath_dev/superset_config_docker.py%5D%0A%20%20%20%60%60%60%0A%20%20%20If%20you%20see%20%22Loaded%20your%20LOCAL%20configuration%22%20instead%2C%20that%27s%20the%20problem.%0A%0A2.%20%2A%2ACheck%20Celery%20beat/worker%20logs%2A%2A%20for%20%60reports.scheduler%60%20tasks.%20If%20these%20don%27t%20appear%2C%20the%20scheduler%20isn%27t%20running%20at%20all.%0A%0A3.%20%2A%2AVerify%20feature%20flags%20aren%27t%20being%20overridden%2A%2A%20by%20environment%20variables%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20exec%20%3Ccontainer%3E%20python%20-c%20%22from%20superset%20import%20app%3B%20print%28app.config%5B%27ALERT_REPORTS%27%5D%29%22%0A%20%20%20docker%20exec%20%3Ccontainer%3E%20python%20-c%20%22from%20superset%20import%20app%3B%20print%28app.config%5B%27ALERT_REPORTS_NOTIFICATION_DRY_RUN%27%5D%29%22%0A%20%20%20%60%60%60%0A%0A4.%20%2A%2ATry%20%22Run%20Now%22%2A%2A%20on%20the%20report%20from%20the%20UI%20%E2%80%94% 20if%20that%20works%2C%20the%20issue%20is%20scheduling%20rather%20than%20execution.%0A%0A5.%20%2A%2ACheck%20if%20the%20report%20is%20stuck%20in%20WORKING%20state%2A%2A%20from%20a%20previous%20run.%20%5BReports%20can%20get%20stuck%5D%28https%3A//github.com/apache/superset/discussions/34121%29%20if%20Celery%20workers%20became%20unhealthy.%20Restarting%20workers%20can%20clear%20this.%0A%0ASince%20your%209am%20reports%20worked%2C%20also%20verify%3A%0A-%20The%204pm%20report%20is%20still%20marked%20as%20%60active%60%20in%20the%20database%0A-%20The%20crontab%20expression%20is%20correct%0A-%20%5BTimezone%20settings%20are%20consistent%5D%28https%3A//github.com/apache/superset/issues/26962%29%20%E2%80%94%20try%20setting%20%60TZ%3DUTC%60%20in%20your%20Docker%20environment%20and%20keeping%20your%20report%20timezone%20as%20UTC) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/38216) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
