GitHub user dosubot[bot] added a comment to the discussion: Unable to configure and get alerts/report via email/slack
<!-- Answer --> If the execution log only shows the start of the run with no error or value, this usually means the report pipeline hit a silent failure—often in authentication, screenshot generation, or notification delivery. Superset relies on the EMAIL_REPORTS_USER being able to access the dashboard/chart; if this user can't log in or doesn't have access, the WebDriver session may fail without a clear error. The authentication for scheduled reports uses a MachineAuthProvider that injects session cookies for the user, so any issue here (like a failed login or missing permissions) can block the report without surfacing an error in the UI or logs [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/machine_auth.py)]. Here’s what to check next: - Manually log in as EMAIL_REPORTS_USER and confirm you can access the dashboard/chart. - Inspect the Superset and Celery worker logs for any tracebacks or info messages like “Report sent to email, notification content is ...” during report execution [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/reports/notifications/email.py)]. - Query the report_execution_log table in your metadata database for recent executions—look for state, error_message, and value fields to see if any errors are recorded that don’t show in the UI. - Test SMTP and Slack connectivity from inside the worker container with a simple Python script to rule out network/config issues. - Double-check that your custom WEBDRIVER_AUTH_FUNC is actually authenticating the WebDriver as the correct user and not just visiting a health endpoint. Silent failures are often due to authentication/session problems or screenshot timeouts. If you still see no errors after these checks, let me know what you find in the logs and database—there may be a subtle config or permission issue blocking report delivery. <!-- 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/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6141786b-7111-424f-9a82-84f2d14434f9?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-14276484 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
