// troubleshooting guide · apache superset

Superset Alerts and Reports Not Sending Emails

Status
Workaround available
platforms:
Self-hosted, Docker, Kubernetes
updated:
November 16, 2026
reports:
4
Method
how we research
Share

RUNBOOK · apache-superset/alerts-reports-not-sending5 FIXES

// quick answer

Superset reports usually fail silently because the ALERT_REPORTS flag, Celery beat schedule, headless browser or SMTP is not set up, or dry-run mode is still on. Check the worker logs first.

Most likely fix: Enable the feature and scheduler

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Enable the feature and scheduler

    1. 01Add 'ALERT_REPORTS': True to FEATURE_FLAGS
    2. 02Add reports.scheduler to CeleryConfig.beat_schedule (every minute)
    3. 03Run exactly one celery beat and at least one celery worker
    Did this fix it?
  2. FIX 2Turn off dry run

    1. 01Set ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
    2. 02Restart the worker and beat
    Did this fix it?
  3. FIX 3Point the worker at Superset

    1. 01Set WEBDRIVER_BASEURL to the internal URL (e.g. http://superset:8088 in Docker, not localhost)
    2. 02Set WEBDRIVER_BASEURL_USER_FRIENDLY to the public URL
    3. 03curl the report URL from the worker container to test
    Did this fix it?
  4. FIX 4Fix screenshots

    1. 01Use the default image, not -lean or -dev, so Playwright and Chromium are included
    2. 02Look for 'Playwright is required' or 'Failed to launch the headless browser' in logs
    Did this fix it?
  5. FIX 5Test SMTP

    1. 01Set SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_MAIL_FROM
    2. 02Send a test email from a Python shell in the worker
    3. 03A 'Connection timed out' usually means the host blocks the SMTP port
    Did this fix it?

SANDBOX · apache-superset RUNS IN YOUR BROWSER

Try it: browse a sample shop and watch visitors, funnels and live data arrive

A hands-on Apache Superset-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

Scheduled reports show as working or failed but no email or Slack message arrives, the Alerts & Reports menu is missing, or screenshots are blank.

Why it happens

  • C-01ALERT_REPORTS feature flag not enabled
  • C-02No reports.scheduler entry in the Celery beat_schedule
  • C-03ALERT_REPORTS_NOTIFICATION_DRY_RUN still True (dev default)
  • C-04Worker cannot reach WEBDRIVER_BASEURL
  • C-05Playwright/Chromium missing in lean images
  • C-06SMTP blocked or misconfigured

// this guide also covers

  • superset alerts and reports not working
  • superset email report not sending
  • superset reports celery beat
  • superset scheduled reports

Still not working?

If Apache Superset keeps failing, you're not alone. See every Apache Superset problem users report or the alternatives people switch to.

Done fighting Apache Superset? Our small team builds your own Apache Superset alternative, or any software you need: web, mobile, games, desktop. Price agreed together.

Talk to us

Watch Apache Superset Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

The same problem in other apps

All notifications, reminders & messages not sending guides →

Other Apache Superset errors

All 14 Apache Superset errors and fixes →