GitHub user Hariprasath-0018 added a comment to the discussion: Alerts and
Reports Emails Not Sending
Hi Dosu,
This is my config file
# Feature flags
FEATURE_FLAGS = {
"ALERT_REPORTS": True,
"PLAYWRIGHT_REPORTS_AND_THUMBNAILS": True,
}
ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
# Celery configuration
from celery.schedules import crontab
class CeleryConfig:
broker_url = "redis://redis:6379/0"
result_backend = "redis://redis:6379/0"
worker_concurrency = 4
beat_schedule = {
"reports.scheduler": {
"task": "reports.scheduler",
"schedule": crontab(minute="*", hour="*"),
},
"reports.prune_log": {
"task": "reports.prune_log",
"schedule": crontab(minute=10, hour=0),
},
}
# Playwright / Chromium (for screenshots)
SUPERSET_FEATURE_PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True
# SMTP configuration
SMTP_HOST = "smtp.yourmail.com"
SMTP_STARTTLS = True
SMTP_SSL = False
SMTP_USER = ***@***.***"
SMTP_PORT = 587
SMTP_PASSWORD = "password"
SMTP_MAIL_FROM = ***@***.***"
Thanks,
Hariprasath
On Thu, 22 Jan, 2026, 7:17 pm dosubot[bot], ***@***.***>
wrote:
> *dosubot[bot]* left a comment (apache/superset#37357)
> <https://github.com/apache/superset/issues/37357#issuecomment-3784509364>
>
> Let's dig deeper since some config is now picked up but emails still
> aren't sent. Here’s what will help pinpoint the issue:
>
> 1. Please share (with sensitive info redacted) the relevant parts of
> your superset_config_docker.py: the FEATURE_FLAGS, CeleryConfig, and
> all SMTP_* settings.
> 2. After restarting, do your logs show Loaded your Docker
> configuration at [...]? If not, the override isn’t loaded.
> 3. In your worker container, run env | grep
> ALERT_REPORTS_NOTIFICATION_DRY_RUN and confirm it is False. If this is
> True in the environment, emails will never be sent—even if the config
> file says False (source
> <https://github.com/apache/superset/issues/32001>).
> 4. Check your Celery worker and beat logs for lines mentioning
> reports.scheduler, reports.execute, or any errors around the time a
> report should trigger. If you never see reports.execute, the scheduler
> isn’t queuing jobs (source
>
> <https://github.com/apache/superset/discussions/35138#discussioncomment-14400023>
> ).
> 5. Is the ReportExecutionLog table still empty after a scheduled
> report should have run? If not, share any error messages found there.
>
> Once you provide this info, I can help you zero in on what’s blocking
> email delivery.
>
> *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.*
> ------------------------------
>
> How did I do? Good
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=great_response>
> | Irrelevant
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=irrelevant_answer>
> | Incorrect
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=incorrect_sources>
> | Verbose
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=too_verbose>
> | Hallucination
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=hallucination>
> | Report 🐛
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=bug_report>
> | Other
> <https://app.dosu.dev/response-feedback/1663c6e2-7e47-40e9-b0d7-68f28d33f1dc?feedback_type=other>
>
> [image: Chat with Dosu]
> <https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github>
> [image: Open in Cursor]
> <https://cursor.com/link/prompt?text=Let%27s%20dig%20deeper%20since%20some%20config%20is%20now%20picked%20up%20but%20emails%20still%20aren%27t%20sent.%20Here%E2%80%99s%20what%20will%20help%20pinpoint%20the%20issue%3A%0A%0A1.%20Please%20share%20%28with%20sensitive%20info%20redacted%29%20the%20relevant%20parts%20of%20your%20%60superset_config_docker.py%60%3A%20the%20%60FEATURE_FLAGS%60%2C%20%60CeleryConfig%60%2C%20and%20all%20%60SMTP_%2A%60%20settings.%0A2.%20After%20restarting%2C%20do%20your%20logs%20show%20%60Loaded%20your%20Docker%20configuration%20at%20%5B...%5D%60%3F%20If%20not%2C%20the%20override%20isn%E2%80%99t%20loaded.%0A3.%20In%20your%20worker%20container%2C%20run%20%60env%20%7C%20grep%20ALERT_REPORTS_NOTIFICATION_DRY_RUN%60%20and%20confirm%20it%20is%20%60False%60.%20If%20this%20is%20%60True%60%20in%20the%20environment%2C%20emails%20will%20never%20be%20sent%E2%80%94even%20if%20the%20config%20file%20says%20%60False%60%20%28%5Bsource%5D%28https%3A//github.com/apache/superset/
issues/32001%29%29.%0A4.%20Check%20your%20Celery%20worker%20and%20beat%20logs%20for%20lines%20mentioning%20%60reports.scheduler%60%2C%20%60reports.execute%60%2C%20or%20any%20errors%20around%20the%20time%20a%20report%20should%20trigger.%20If%20you%20never%20see%20%60reports.execute%60%2C%20the%20scheduler%20isn%E2%80%99t%20queuing%20jobs%20%28%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/35138%23discussioncomment-14400023%29%29.%0A5.%20Is%20the%20%60ReportExecutionLog%60%20table%20still%20empty%20after%20a%20scheduled%20report%20should%20have%20run%3F%20If%20not%2C%20share%20any%20error%20messages%20found%20there.%0A%0AOnce%20you%20provide%20this%20info%2C%20I%20can%20help%20you%20zero%20in%20on%20what%E2%80%99s%20blocking%20email%20delivery.>
> [image: Join Discord] <https://go.dosu.dev/discord-bot> [image: Share on
> X]
> <https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37357>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/superset/issues/37357#issuecomment-3784509364>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCNYORWXOFORJOABR4VMHPT4IDIIBAVCNFSM6AAAAACSQNNHUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBUGUYDSMZWGQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
GitHub link:
https://github.com/apache/superset/discussions/37401#discussioncomment-15583327
----
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]
