Bug description

i deploy superset with default docker-compose.yml.playwrith for screenshot,Unable to send email successfully and nothong error info ； config ： FEATURE_FLAGS = { 'PRESTO_EXPAND_DATA': False, 'ENABLE_TEMPLATE_PROCESSING': True, 'FAB_API_SWAGGER_UI' : True, 'ALERT_REPORTS' : True, 'ALERT_REPORTS_NOTIFICATION_DRY_RUN' :False, #"THUMBNAILS": True, "ALERT_REPORT_TABS" :True, #"THUMBNAILS_SQLA_LISTENERS": True, "ALERT_REPORTS_FILTER" :True, "ENABLE_DASHBOARD_DOWNLOAD_WEBDRIVER_SCREENSHOT": True, "ENABLE_DASHBOARD_SCREENSHOT_ENDPOINTS": True, "DYNAMIC_PLUGINS" :True, "DASHBOARD_RBAC" :True, "PLAYWRIGHT_REPORTS_AND_THUMBNAILS":True } WEBDRIVER_BASEURL = "http://superset_app:8088" # When running using docker compose use "http://superset_app:8088'

This is the link sent to the recipient. Change to your domain, e.g. https://superset.mydomain.com

WEBDRIVER_BASEURL_USER_FRIENDLY = "http://localhost:8088"

Screenshots/recordings

Image

Image

Image

Superset version

master / latest-dev

Python version

3.11

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

  • [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
  • [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Comment From: dosubot[bot]

Hi @clp007! I'm Dosu and I’m helping the superset team.

The most common reason for reports not sending emails in Superset (especially with docker-compose) is the ALERT_REPORTS_NOTIFICATION_DRY_RUN setting. In many Docker setups, this defaults to True, which means emails are never actually sent, but no error is shown. You have set it to False, which is correct—just make sure this is set in your actual superset_config.py or superset_config_docker.py and that the file is mounted or copied into your container as expected. If it's not picked up, Superset will silently stay in dry-run mode and not send emails, even though everything else looks fine (source).

If dry-run is definitely off, the next most likely cause is SMTP misconfiguration. Superset needs working SMTP settings (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_MAIL_FROM, etc). The default config points to localhost:25, which usually won’t work unless you have a local mail server running in your Docker network. You can test your SMTP settings with a simple Python script to confirm connectivity (example and troubleshooting).

Also, check that your Celery workers are running and connected, and that your network/firewall allows outbound SMTP connections. If you still don’t see errors, check the ReportExecutionLog table in your Superset database for hidden error messages.

Let me know if you want a sample SMTP test script or more details on any of these steps.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X