Hariprasath-0018 opened a new issue, #37357:
URL: https://github.com/apache/superset/issues/37357
### Bug description
I'm facing in setting up alerts and reports in Apache Superset. I've
followed the documentation and various troubleshooting steps, but emails are
still not being sent, and it seems the reports aren't even triggering as
expected.
**Environment Details:**
Superset Version: I'm using the latest Docker image
(apache/superset:latest), but logs show a dev-like version "0.0.1rc3" (possibly
from editable mode).
Deployment: Docker Compose on Windows with WSL2
(Linux-6.6.87.2-microsoft-standard-WSL2-x86_64).
OS: Windows host, WSL2 subsystem.
Databases/Services: PostgreSQL for metadata, Redis (superset_cache) for
Celery broker/results.
Celery: v5.5.2 (immunity), with worker and scheduler services.
Feature Flags: ALERT_REPORTS: True, ALERT_REPORTS_NOTIFICATION_DRY_RUN:
False.
SMTP Provider: Gmail with app password (port 587, STARTTLS).
**Issue Description:**
Alerts and reports are enabled, but no emails are sent when scheduled. The
SMTP configuration works fine—I successfully tested sending an email manually
from the worker container using a Python script (it printed "Email sent!" and
the email arrived). However:
No tasks appear in the worker logs related to reports (e.g., no
"reports.execute" or "reports.scheduler").
The UI Execution Log shows no entries for the alerts/reports I've created.
Schedules are set to every 5 minutes (cron: */5 * * * *), but nothing
triggers.
This suggests the scheduling or task queuing isn't working, even though
Celery worker and beat start without errors.
**Steps Taken:**
Enabled ALERT_REPORTS in superset_config.py.
Configured SMTP settings (verified with manual test script).
Set up Celery with broker/result_backend on Redis.
Defined beat_schedule in CeleryConfig for reports.scheduler (every minute)
and reports.prune_log.
Installed Playwright manually in the worker container (for screenshots): pip
install playwright, playwright install, and dependencies via apt.
Added a dedicated superset-scheduler service in docker-compose.yml running
celery beat.
Restarted all services multiple times.
Created simple test reports in UI (email delivery, text-only to rule out
visuals).
Checked logs: Worker starts fine ("celery@... ready"), connects to Redis,
but no task activity. Scheduler logs show startup but no evidence of sending
tasks.
### Screenshots/recordings
<img width="1919" height="932" alt="Image"
src="https://github.com/user-attachments/assets/e01062d9-37a2-41e7-ab68-c4f4f9625788";
/>
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
