GitHub user dosubot[bot] added a comment to the discussion: Unable to configure and get alerts/report via email/slack
<!-- Greeting --> Hi @abhijeet-ghl! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> The most common cause for Superset alerts/reports not being delivered (when you only get sample/error mails) is that `ALERT_REPORTS_NOTIFICATION_DRY_RUN` is still enabled in the worker environment. This config must be set to `False` in your Python config (not as an environment variable), and the updated config must be mounted into all relevant pods (web, worker, beat). After changing it, restart all pods to ensure the new config is loaded. If you still get only dry-run/sample messages, check the active config inside your running worker containers—environment variables do not override this setting [[source]](https://github.com/apache/superset/issues/32001). For authentication: scheduled reports run as the user specified in `ALERT_REPORTS_EXECUTORS` (often `EMAIL_REPORTS_USER`, e.g., `platform`). This user must exist, be active, and have access to the dashboards/charts being reported. If the user can't access the dashboard, screenshot generation and report delivery will fail or result in error/sample mails [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/security/manager.py). The HybridSecurityManager approach (bypassing OAuth based on User-Agent) does not work for scheduled reports, because Celery/background tasks do not have HTTP request context—so authentication bypass must be handled structurally, not via request headers [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/initialization/__init__.py). WebDriver authentication for scheduled reports uses a MachineAuthProvider that sets session cookies for the specified user. Make sure your `WEBDRIVER_AUTH_FUNC` is correctly set up to authenticate the WebDriver for offline report generation [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/machine_auth.py). Checklist: - Confirm `ALERT_REPORTS_NOTIFICATION_DRY_RUN = False` in the Python config used by all pods, and restart all pods after changing. - Make sure `EMAIL_REPORTS_USER` exists, is active, and has dashboard/chart access. - Test SMTP and Slack connectivity from the worker container. - Check Celery worker and beat health/status. - Ensure all required feature flags are enabled. - If you use PNG/CSV/text formats, upgrade to a version with the August 2024 bug fix [[source]](https://github.com/apache/superset/pull/30001). If you follow these steps, you should be able to get actual alerts/reports delivered via email and Slack. <!-- 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/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0e0513e7-871f-458b-815e-22eb0bdce941?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/discussions/34943) GitHub link: https://github.com/apache/superset/discussions/34943#discussioncomment-14275925 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
