You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Hariprasath-0018 (via GitHub)" <gi...@apache.org> on 2026/01/22 09:16:50 UTC
[I] Alerts and Reports Emails Not Sending [superset]
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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3784000704
Hi Dosu,
I attempted to create a new file named superset_config_docker.py and then
restarted the Superset container. After that, running superset init failed.
Subsequently, I removed the file and restarted the container again. The
container is now running, but in the logs, I see the following message:
Log - Init Step 1/4 [Starting] -- Applying DB migrations
######################################################################
Loaded your LOCAL configuration at
[/app/docker/pythonpath_dev/superset_config.py]
It seems the container is still picking up a configuration file even after
removing the new file. Could you please advise on how to resolve this issue?
Thanks,
Hariprasath N
On Thu, 22 Jan 2026 at 16:09, dosubot[bot] ***@***.***> wrote:
> *dosubot[bot]* left a comment (apache/superset#37357)
> <https://github.com/apache/superset/issues/37357#issuecomment-3783696072>
>
> Your config changes aren’t being picked up because, in Docker Compose,
> Superset only loads custom config from
> docker/pythonpath_dev/superset_config_docker.py—not from
> superset_config.py elsewhere. This is why your alerts/reports aren’t
> triggering, even though everything looks correct in your current config.
>
> To fix this:
>
> 1. Copy your custom settings (feature flags, CeleryConfig, SMTP,
> Playwright, etc.) into docker/pythonpath_dev/superset_config_docker.py.
> Use superset_config_local.example as a template if needed.
> 2. Restart (or rebuild) all Superset containers.
> 3. Check your container logs for a message like Loaded your Docker
> configuration at [...] to confirm the override is loaded. If you see Using
> default Docker config..., your override wasn’t found.
> 4. Once loaded, your scheduled reports and emails should start working
> as expected.
>
> More details and confirmation of this config loading behavior are in the official
> Docker README
> <https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md#L31-L39>
> and docker config file
> <https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py#L18-L138>
> .
>
> Let me know if moving your config and restarting fixes the issue!
>
> *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.*
> ------------------------------
>
> How did I do? Good
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=great_response>
> | Irrelevant
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=irrelevant_answer>
> | Incorrect
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=incorrect_sources>
> | Verbose
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=too_verbose>
> | Hallucination
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=hallucination>
> | Report 🐛
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=bug_report>
> | Other
> <https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?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=Your%20config%20changes%20aren%E2%80%99t%20being%20picked%20up%20because%2C%20in%20Docker%20Compose%2C%20Superset%20only%20loads%20custom%20config%20from%20%60docker/pythonpath_dev/superset_config_docker.py%60%E2%80%94not%20from%20%60superset_config.py%60%20elsewhere.%20This%20is%20why%20your%20alerts/reports%20aren%E2%80%99t%20triggering%2C%20even%20though%20everything%20looks%20correct%20in%20your%20current%20config.%0A%0ATo%20fix%20this%3A%0A1.%20Copy%20your%20custom%20settings%20%28feature%20flags%2C%20CeleryConfig%2C%20SMTP%2C%20Playwright%2C%20etc.%29%20into%20%60docker/pythonpath_dev/superset_config_docker.py%60.%20Use%20%60superset_config_local.example%60%20as%20a%20template%20if%20needed.%0A2.%20Restart%20%28or%20rebuild%29%20all%20Superset%20containers.%0A3.%20Check%20your%20container%20logs%20for%20a%20message%20like%20%60Loaded%20your%20Docker%20configuration%20at%20%5B...%5D%60%20to%20confirm%20the%20override%20is%20loaded.%20If%
20you%20see%20%60Using%20default%20Docker%20config...%60%2C%20your%20override%20wasn%E2%80%99t%20found.%0A4.%20Once%20loaded%2C%20your%20scheduled%20reports%20and%20emails%20should%20start%20working%20as%20expected.%0A%0AMore%20details%20and%20confirmation%20of%20this%20config%20loading%20behavior%20are%20in%20the%20%5Bofficial%20Docker%20README%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md%23L31-L39%29%20and%20%5Bdocker%20config%20file%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py%23L18-L138%29.%0A%0ALet%20me%20know%20if%20moving%20your%20config%20and%20restarting%20fixes%20the%20issue%21>
> [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-3783696072>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCNYORXIF7GXQ2GYYDZXQE34ICSGVAVCNFSM6AAAAACSQNNHUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBTGY4TMMBXGI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3788625014
Hi Sam/Dosu,
The Report and Alert are both being triggered successfully. However, in the
logs, I still see the following error:
Failed taking a screenshot 'NoneType' object is not callable
I have already installed *Playwright* and *Chromium* inside the container.
Could you help identify what might be causing this issue?
Thanks,
Hariprasath
On Thu, 22 Jan 2026 at 23:56, Sam Firke ***@***.***> wrote:
> *sfirke* left a comment (apache/superset#37357)
> <https://github.com/apache/superset/issues/37357#issuecomment-3786007470>
>
> Hello, this appears to be a Q&A request for help rather than a bug report.
> I would suggest for starters running an official release docker image like
> apache/superset:6.0.0. I can verify that Alerts & Reports work great with
> a docker compose deployment and that version, so this is a matter of your
> configuration rather than a bug in Superset.
>
> Feel free to work with Dosu, there's also the #ask-ai channel in Superset
> Slack. But I am inclined to convert this to a discussion, though, as it
> doesn't need to be in our bug tracker.
>
> If, when you get this resolved, you find there's something we should add
> to the docs, we'd love if you could add it!
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/superset/issues/37357#issuecomment-3786007470>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCNYORUAGQP6OSD7ZJJLO5D4IEI4RAVCNFSM6AAAAACSQNNHUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBWGAYDONBXGA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke closed issue #37357: Alerts and Reports Emails Not Sending
URL: https://github.com/apache/superset/issues/37357
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3784509364
<!-- Answer -->
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.
<!-- 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/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)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](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.) [](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/issues/37357)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3783670095
Hi @dosu Thanks for the detailed checklist! I went through each point and here’s the status of my Superset setup:
1. Config file placement:
I don’t have a superset_config_docker.py in my directory. The files I have are:
superset_config.py
superset_config_docker_light.py
superset_config_local.example
superset_test_config_light.py
2. Feature flags: ✅ Already done.
3. Celery beat schedule: ✅ Already done.
4. Playwright/Chromium:
Installed manually, but had to change .env to:
ENABLE_PLAYWRIGHT=true
INCLUDE_CHROMIUM=true
before it would recognize Playwright.
5. SMTP config: ✅ Already done.
6. Database migrations: ✅ Tables migrated successfully.
7. Active schedules: ✅ Schedules are active.
8. Logs:
Worker starts fine (celery@... ready) and connects to Redis. Scheduler logs show startup, but there’s no evidence of tasks being sent.
9. Execution logs:
ReportExecutionLog table is empty.
Despite everything above being configured, emails are still not being sent.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3783679235
Hi @dosu Thanks for the detailed checklist! I went through each point and
here’s the status of my Superset setup:
*1. Config file placement:*
I don’t have a standard superset_config_docker.py in my directory. The
files I have are:
* superset_config.py
-
superset_config_docker_light.py
-
superset_config_local.example
-
superset_test_config_light.py
*2. Feature flags:* ✅ Already done.
*3. Celery beat schedule:* ✅ Already done.
*4. Playwright/Chromium:*
Installed manually, but had to change .env to:
ENABLE_PLAYWRIGHT=trueINCLUDE_CHROMIUM=true
before it would recognize Playwright.
*5. SMTP config:* ✅ Already done.
*6. Database migrations:* ✅ Tables migrated successfully.
*7. Active schedules:* ✅ Schedules are active.
*8. Logs:*
Worker starts fine ***@***.*** ready) and connects to Redis. Scheduler logs
show startup, but there’s no evidence of tasks being sent.
*9. Execution logs:*
ReportExecutionLog table is empty.
Despite everything above being configured, emails are still not being sent.
On Thu, 22 Jan 2026 at 14:51, dosubot[bot] ***@***.***> wrote:
> *dosubot[bot]* left a comment (apache/superset#37357)
> <https://github.com/apache/superset/issues/37357#issuecomment-3783371569>
>
> Hi @Hariprasath-0018 <https://github.com/Hariprasath-0018>! I'm Dosu
> <https://go.dosu.dev/dosubot> and I’m helping the superset team.
>
> Here’s a focused checklist to help you pinpoint why alerts/reports aren’t
> triggering or sending emails in your Superset setup:
>
> 1.
>
> *Config file placement:* In Docker Compose, Superset only loads custom
> config from docker/pythonpath_dev/superset_config_docker.py. If you’re
> editing another file (like superset_config.py elsewhere), your changes
> (e.g., ALERT_REPORTS, ALERT_REPORTS_NOTIFICATION_DRY_RUN,
> CeleryConfig) may not be picked up. Double-check the config is in the right
> place and mounted correctly in your containers (source)
> <https://github.com/apache/superset/discussions/35178#discussioncomment-14443403>
> .
> 2.
>
> *Feature flags:* Make sure ALERT_REPORTS is True and
> ALERT_REPORTS_NOTIFICATION_DRY_RUN is False in the loaded config. If
> dry-run is enabled (or not set in the right file), Superset will silently
> skip sending emails (source)
> <https://github.com/apache/superset/issues/33815>.
> 3.
>
> *Celery beat schedule:* Your CeleryConfig must include a beat_schedule
> with at least:
>
> class CeleryConfig:
> beat_schedule = {
> "reports.scheduler": {
> "task": "reports.scheduler",
> "schedule": crontab(minute="*", hour="*"),
> },
> "reports.prune_log": {
> "task": "reports.prune_log",
> "schedule": crontab(minute=10, hour=0),
> },
> }
>
> If this is missing or not loaded, scheduled reports won’t run (source)
> <https://github.com/apache/superset/discussions/31647>.
> 4.
>
> *Playwright/Chromium:* For screenshots, Playwright is now recommended.
> You must:
> - Install Playwright and Chromium in the worker container (pip install
> playwright && playwright install chromium).
> - Set SUPERSET_FEATURE_PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True in
> your config.
> - In Docker, set ENABLE_PLAYWRIGHT=true and INCLUDE_CHROMIUM=true
> in docker/.env, then rebuild your images.
> - Test with playwright show-browser chromium and playwright
> screenshot http://superset:8088/ /tmp/test.png inside the worker
> container (source)
> <https://github.com/apache/superset/discussions/35327>.
> 5.
>
> *SMTP config:* Confirm all SMTP settings are correct in your config
> file (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_MAIL_FROM,
> SMTP_STARTTLS, etc.). Manual Python script tests are good, but
> Superset must use the same config (source)
> <https://github.com/apache/superset/issues/33815>.
> 6.
>
> *Database migrations:* Make sure all migrations are applied and the
> following tables exist and are populated: report_schedule,
> report_recipient, report_execution_log. If these are missing, reports
> can’t be scheduled or executed.
> 7.
>
> *Active schedules:* Check that your reports/alerts are active in the
> DB (active = True in report_schedule). If there are no active
> schedules, nothing will trigger.
> 8.
>
> *Logs:* Look for reports.scheduler and reports.execute in your Celery
> worker and beat logs. If you see the scheduler but not execute, the
> scheduler isn’t queuing jobs. If you see neither, the beat schedule or
> feature flag is likely not loaded.
> 9.
>
> *Execution logs:* Check the ReportExecutionLog table in your metadata
> DB for error messages or silent failures. This often reveals issues not
> visible in the UI.
>
> If any step fails, focus on fixing that before moving on. If everything
> looks correct but nothing triggers, try:
>
> - Forcing a config reload (rebuild/restart all containers).
> - Verifying the config is loaded by running print(app.config) in a
> Superset shell inside the container.
> - Checking for any errors or warnings in the logs right after
> container startup.
>
> Let me know what you find at each step—this will help narrow down the root
> cause!
>
> *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.*
> ------------------------------
>
> How did I do? Good
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=great_response>
> | Irrelevant
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=irrelevant_answer>
> | Incorrect
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=incorrect_sources>
> | Verbose
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=too_verbose>
> | Hallucination
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=hallucination>
> | Report 🐛
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=bug_report>
> | Other
> <https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?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=Here%E2%80%99s%20a%20focused%20checklist%20to%20help%20you%20pinpoint%20why%20alerts/reports%20aren%E2%80%99t%20triggering%20or%20sending%20emails%20in%20your%20Superset%20setup%3A%0A%0A1.%20%2A%2AConfig%20file%20placement%3A%2A%2A%20In%20Docker%20Compose%2C%20Superset%20only%20loads%20custom%20config%20from%20%60docker/pythonpath_dev/superset_config_docker.py%60.%20If%20you%E2%80%99re%20editing%20another%20file%20%28like%20%60superset_config.py%60%20elsewhere%29%2C%20your%20changes%20%28e.g.%2C%20%60ALERT_REPORTS%60%2C%20%60ALERT_REPORTS_NOTIFICATION_DRY_RUN%60%2C%20CeleryConfig%29%20may%20not%20be%20picked%20up.%20Double-check%20the%20config%20is%20in%20the%20right%20place%20and%20mounted%20correctly%20in%20your%20containers%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/discussions/35178%23discussioncomment-14443403%29.%0A%0A2.%20%2A%2AFeature%20flags%3A%2A%2A%20Make%20sure%20%60ALERT_REPORTS%60%20is%20%60True%60%20and%20%60AL
ERT_REPORTS_NOTIFICATION_DRY_RUN%60%20is%20%60False%60%20in%20the%20loaded%20config.%20If%20dry-run%20is%20enabled%20%28or%20not%20set%20in%20the%20right%20file%29%2C%20Superset%20will%20silently%20skip%20sending%20emails%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/33815%29.%0A%0A3.%20%2A%2ACelery%20beat%20schedule%3A%2A%2A%20Your%20%60CeleryConfig%60%20must%20include%20a%20%60beat_schedule%60%20with%20at%20least%3A%0A%20%20%20%60%60%60python%0A%20%20%20class%20CeleryConfig%3A%0A%20%20%20%20%20%20%20beat_schedule%20%3D%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%22reports.scheduler%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22task%22%3A%20%22reports.scheduler%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22schedule%22%3A%20crontab%28minute%3D%22%2A%22%2C%20hour%3D%22%2A%22%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%22reports.prune_log%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22t
ask%22%3A%20%22reports.prune_log%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22schedule%22%3A%20crontab%28minute%3D10%2C%20hour%3D0%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%7D%0A%20%20%20%60%60%60%0A%20%20%20If%20this%20is%20missing%20or%20not%20loaded%2C%20scheduled%20reports%20won%E2%80%99t%20run%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/discussions/31647%29.%0A%0A4.%20%2A%2APlaywright/Chromium%3A%2A%2A%20For%20screenshots%2C%20Playwright%20is%20now%20recommended.%20You%20must%3A%0A%20%20%20-%20Install%20Playwright%20and%20Chromium%20in%20the%20worker%20container%20%28%60pip%20install%20playwright%20%26%26%20playwright%20install%20chromium%60%29.%0A%20%20%20-%20Set%20%60SUPERSET_FEATURE_PLAYWRIGHT_REPORTS_AND_THUMBNAILS%20%3D%20True%60%20in%20your%20config.%0A%20%20%20-%20In%20Docker%2C%20set%20%60ENABLE_PLAYWRIGHT%3Dtrue%60%20and%20%60INCLUDE_CHROMIUM%3Dtrue%60%20in%20%60docker/.env%60%2C%20then%20rebuild%20your%20images.
%0A%20%20%20-%20Test%20with%20%60playwright%20show-browser%20chromium%60%20and%20%60playwright%20screenshot%20http%3A//superset%3A8088/%20/tmp/test.png%60%20inside%20the%20worker%20container%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/discussions/35327%29.%0A%0A5.%20%2A%2ASMTP%20config%3A%2A%2A%20Confirm%20all%20SMTP%20settings%20are%20correct%20in%20your%20config%20file%20%28%60SMTP_HOST%60%2C%20%60SMTP_PORT%60%2C%20%60SMTP_USER%60%2C%20%60SMTP_PASSWORD%60%2C%20%60SMTP_MAIL_FROM%60%2C%20%60SMTP_STARTTLS%60%2C%20etc.%29.%20Manual%20Python%20script%20tests%20are%20good%2C%20but%20Superset%20must%20use%20the%20same%20config%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/33815%29.%0A%0A6.%20%2A%2ADatabase%20migrations%3A%2A%2A%20Make%20sure%20all%20migrations%20are%20applied%20and%20the%20following%20tables%20exist%20and%20are%20populated%3A%20%60report_schedule%60%2C%20%60report_recipient%60%2C%20%60report_execution_log%60.%20If%20these%20are%20miss
ing%2C%20reports%20can%E2%80%99t%20be%20scheduled%20or%20executed.%0A%0A7.%20%2A%2AActive%20schedules%3A%2A%2A%20Check%20that%20your%20reports/alerts%20are%20active%20in%20the%20DB%20%28%60active%20%3D%20True%60%20in%20%60report_schedule%60%29.%20If%20there%20are%20no%20active%20schedules%2C%20nothing%20will%20trigger.%0A%0A8.%20%2A%2ALogs%3A%2A%2A%20Look%20for%20%60reports.scheduler%60%20and%20%60reports.execute%60%20in%20your%20Celery%20worker%20and%20beat%20logs.%20If%20you%20see%20the%20scheduler%20but%20not%20execute%2C%20the%20scheduler%20isn%E2%80%99t%20queuing%20jobs.%20If%20you%20see%20neither%2C%20the%20beat%20schedule%20or%20feature%20flag%20is%20likely%20not%20loaded.%0A%0A9.%20%2A%2AExecution%20logs%3A%2A%2A%20Check%20the%20%60ReportExecutionLog%60%20table%20in%20your%20metadata%20DB%20for%20error%20messages%20or%20silent%20failures.%20This%20often%20reveals%20issues%20not%20visible%20in%20the%20UI.%0A%0AIf%20any%20step%20fails%2C%20focus%20on%20fixing%20that%20before%2
0moving%20on.%20If%20everything%20looks%20correct%20but%20nothing%20triggers%2C%20try%3A%0A-%20Forcing%20a%20config%20reload%20%28rebuild/restart%20all%20containers%29.%0A-%20Verifying%20the%20config%20is%20loaded%20by%20running%20%60print%28app.config%29%60%20in%20a%20Superset%20shell%20inside%20the%20container.%0A-%20Checking%20for%20any%20errors%20or%20warnings%20in%20the%20logs%20right%20after%20container%20startup.%0A%0ALet%20me%20know%20what%20you%20find%20at%20each%20step%E2%80%94this%20will%20help%20narrow%20down%20the%20root%20cause%21>
> [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-3783371569>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCNYORQ6YHVQFRCSWHN5NBT4ICJDBAVCNFSM6AAAAACSQNNHUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBTGM3TCNJWHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3783371569
<!-- Greeting -->
Hi @Hariprasath-0018! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Here’s a focused checklist to help you pinpoint why alerts/reports aren’t triggering or sending emails in your Superset setup:
1. **Config file placement:** In Docker Compose, Superset only loads custom config from `docker/pythonpath_dev/superset_config_docker.py`. If you’re editing another file (like `superset_config.py` elsewhere), your changes (e.g., `ALERT_REPORTS`, `ALERT_REPORTS_NOTIFICATION_DRY_RUN`, CeleryConfig) may not be picked up. Double-check the config is in the right place and mounted correctly in your containers [(source)](https://github.com/apache/superset/discussions/35178#discussioncomment-14443403).
2. **Feature flags:** Make sure `ALERT_REPORTS` is `True` and `ALERT_REPORTS_NOTIFICATION_DRY_RUN` is `False` in the loaded config. If dry-run is enabled (or not set in the right file), Superset will silently skip sending emails [(source)](https://github.com/apache/superset/issues/33815).
3. **Celery beat schedule:** Your `CeleryConfig` must include a `beat_schedule` with at least:
```python
class CeleryConfig:
beat_schedule = {
"reports.scheduler": {
"task": "reports.scheduler",
"schedule": crontab(minute="*", hour="*"),
},
"reports.prune_log": {
"task": "reports.prune_log",
"schedule": crontab(minute=10, hour=0),
},
}
```
If this is missing or not loaded, scheduled reports won’t run [(source)](https://github.com/apache/superset/discussions/31647).
4. **Playwright/Chromium:** For screenshots, Playwright is now recommended. You must:
- Install Playwright and Chromium in the worker container (`pip install playwright && playwright install chromium`).
- Set `SUPERSET_FEATURE_PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True` in your config.
- In Docker, set `ENABLE_PLAYWRIGHT=true` and `INCLUDE_CHROMIUM=true` in `docker/.env`, then rebuild your images.
- Test with `playwright show-browser chromium` and `playwright screenshot http://superset:8088/ /tmp/test.png` inside the worker container [(source)](https://github.com/apache/superset/discussions/35327).
5. **SMTP config:** Confirm all SMTP settings are correct in your config file (`SMTP_HOST`, `SMTP_PORT`, `SMTP_USER`, `SMTP_PASSWORD`, `SMTP_MAIL_FROM`, `SMTP_STARTTLS`, etc.). Manual Python script tests are good, but Superset must use the same config [(source)](https://github.com/apache/superset/issues/33815).
6. **Database migrations:** Make sure all migrations are applied and the following tables exist and are populated: `report_schedule`, `report_recipient`, `report_execution_log`. If these are missing, reports can’t be scheduled or executed.
7. **Active schedules:** Check that your reports/alerts are active in the DB (`active = True` in `report_schedule`). If there are no active schedules, nothing will trigger.
8. **Logs:** Look for `reports.scheduler` and `reports.execute` in your Celery worker and beat logs. If you see the scheduler but not execute, the scheduler isn’t queuing jobs. If you see neither, the beat schedule or feature flag is likely not loaded.
9. **Execution logs:** Check the `ReportExecutionLog` table in your metadata DB for error messages or silent failures. This often reveals issues not visible in the UI.
If any step fails, focus on fixing that before moving on. If everything looks correct but nothing triggers, try:
- Forcing a config reload (rebuild/restart all containers).
- Verifying the config is loaded by running `print(app.config)` in a Superset shell inside the container.
- Checking for any errors or warnings in the logs right after container startup.
Let me know what you find at each step—this will help narrow down the root cause!
<!-- 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/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/88bc3ee0-db43-4eeb-bc95-2541b6845527?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Here%E2%80%99s%20a%20focused%20checklist%20to%20help%20you%20pinpoint%20why%20alerts/reports%20aren%E2%80%99t%20triggering%20or%20sending%20emails%20in%20your%20Superset%20setup%3A%0A%0A1.%20%2A%2AConfig%20file%20placement%3A%2A%2A%20In%20Docker%20Compose%2C%20Superset%20only%20loads%20custom%20config%20from%20%60docker/pythonpath_dev/superset_config_docker.py%60.%20If%20you%E2%80%99re%20editing%20another%20file%20%28like%20%60superset_config.py%60%20elsewhere%29%2C%20your%20changes%20%28e.g.%2C%20%60ALERT_REPORTS%60%2C%20%60ALERT_REPORTS_NOTIFICATION_DRY_RUN%60%2C%20CeleryConfig%29%20may%20not%20be%20picked%20up.%20Double-check%20the%20config%20is%20in%20the%20right%20place%20and%20mounted%20correctly%20in%20your%20containers%20%5B%28source%29%5D%
28https%3A//github.com/apache/superset/discussions/35178%23discussioncomment-14443403%29.%0A%0A2.%20%2A%2AFeature%20flags%3A%2A%2A%20Make%20sure%20%60ALERT_REPORTS%60%20is%20%60True%60%20and%20%60ALERT_REPORTS_NOTIFICATION_DRY_RUN%60%20is%20%60False%60%20in%20the%20loaded%20config.%20If%20dry-run%20is%20enabled%20%28or%20not%20set%20in%20the%20right%20file%29%2C%20Superset%20will%20silently%20skip%20sending%20emails%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/33815%29.%0A%0A3.%20%2A%2ACelery%20beat%20schedule%3A%2A%2A%20Your%20%60CeleryConfig%60%20must%20include%20a%20%60beat_schedule%60%20with%20at%20least%3A%0A%20%20%20%60%60%60python%0A%20%20%20class%20CeleryConfig%3A%0A%20%20%20%20%20%20%20beat_schedule%20%3D%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%22reports.scheduler%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22task%22%3A%20%22reports.scheduler%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22schedule%22%3A%20crontab%28minute%3D%
22%2A%22%2C%20hour%3D%22%2A%22%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%22reports.prune_log%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22task%22%3A%20%22reports.prune_log%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22schedule%22%3A%20crontab%28minute%3D10%2C%20hour%3D0%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%7D%0A%20%20%20%60%60%60%0A%20%20%20If%20this%20is%20missing%20or%20not%20loaded%2C%20scheduled%20reports%20won%E2%80%99t%20run%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/discussions/31647%29.%0A%0A4.%20%2A%2APlaywright/Chromium%3A%2A%2A%20For%20screenshots%2C%20Playwright%20is%20now%20recommended.%20You%20must%3A%0A%20%20%20-%20Install%20Playwright%20and%20Chromium%20in%20the%20worker%20container%20%28%60pip%20install%20playwright%20%26%26%20playwright%20install%20chromium%60%29.%0A%20%20%20-%20Set%20%60SUPERSET_FEATURE_PLAYWRIGHT_REPORTS_AND_THUMBNAILS%20%3D%20
True%60%20in%20your%20config.%0A%20%20%20-%20In%20Docker%2C%20set%20%60ENABLE_PLAYWRIGHT%3Dtrue%60%20and%20%60INCLUDE_CHROMIUM%3Dtrue%60%20in%20%60docker/.env%60%2C%20then%20rebuild%20your%20images.%0A%20%20%20-%20Test%20with%20%60playwright%20show-browser%20chromium%60%20and%20%60playwright%20screenshot%20http%3A//superset%3A8088/%20/tmp/test.png%60%20inside%20the%20worker%20container%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/discussions/35327%29.%0A%0A5.%20%2A%2ASMTP%20config%3A%2A%2A%20Confirm%20all%20SMTP%20settings%20are%20correct%20in%20your%20config%20file%20%28%60SMTP_HOST%60%2C%20%60SMTP_PORT%60%2C%20%60SMTP_USER%60%2C%20%60SMTP_PASSWORD%60%2C%20%60SMTP_MAIL_FROM%60%2C%20%60SMTP_STARTTLS%60%2C%20etc.%29.%20Manual%20Python%20script%20tests%20are%20good%2C%20but%20Superset%20must%20use%20the%20same%20config%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/33815%29.%0A%0A6.%20%2A%2ADatabase%20migrations%3A%2A%2A%20Make%20sure%20all%20migrati
ons%20are%20applied%20and%20the%20following%20tables%20exist%20and%20are%20populated%3A%20%60report_schedule%60%2C%20%60report_recipient%60%2C%20%60report_execution_log%60.%20If%20these%20are%20missing%2C%20reports%20can%E2%80%99t%20be%20scheduled%20or%20executed.%0A%0A7.%20%2A%2AActive%20schedules%3A%2A%2A%20Check%20that%20your%20reports/alerts%20are%20active%20in%20the%20DB%20%28%60active%20%3D%20True%60%20in%20%60report_schedule%60%29.%20If%20there%20are%20no%20active%20schedules%2C%20nothing%20will%20trigger.%0A%0A8.%20%2A%2ALogs%3A%2A%2A%20Look%20for%20%60reports.scheduler%60%20and%20%60reports.execute%60%20in%20your%20Celery%20worker%20and%20beat%20logs.%20If%20you%20see%20the%20scheduler%20but%20not%20execute%2C%20the%20scheduler%20isn%E2%80%99t%20queuing%20jobs.%20If%20you%20see%20neither%2C%20the%20beat%20schedule%20or%20feature%20flag%20is%20likely%20not%20loaded.%0A%0A9.%20%2A%2AExecution%20logs%3A%2A%2A%20Check%20the%20%60ReportExecutionLog%60%20table%20in%20your%20metad
ata%20DB%20for%20error%20messages%20or%20silent%20failures.%20This%20often%20reveals%20issues%20not%20visible%20in%20the%20UI.%0A%0AIf%20any%20step%20fails%2C%20focus%20on%20fixing%20that%20before%20moving%20on.%20If%20everything%20looks%20correct%20but%20nothing%20triggers%2C%20try%3A%0A-%20Forcing%20a%20config%20reload%20%28rebuild/restart%20all%20containers%29.%0A-%20Verifying%20the%20config%20is%20loaded%20by%20running%20%60print%28app.config%29%60%20in%20a%20Superset%20shell%20inside%20the%20container.%0A-%20Checking%20for%20any%20errors%20or%20warnings%20in%20the%20logs%20right%20after%20container%20startup.%0A%0ALet%20me%20know%20what%20you%20find%20at%20each%20step%E2%80%94this%20will%20help%20narrow%20down%20the%20root%20cause%21) [](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/issues/37357)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3783696072
<!-- Answer -->
Your config changes aren’t being picked up because, in Docker Compose, Superset only loads custom config from `docker/pythonpath_dev/superset_config_docker.py`—not from `superset_config.py` elsewhere. This is why your alerts/reports aren’t triggering, even though everything looks correct in your current config.
To fix this:
1. Copy your custom settings (feature flags, CeleryConfig, SMTP, Playwright, etc.) into `docker/pythonpath_dev/superset_config_docker.py`. Use `superset_config_local.example` as a template if needed.
2. Restart (or rebuild) all Superset containers.
3. Check your container logs for a message like `Loaded your Docker configuration at [...]` to confirm the override is loaded. If you see `Using default Docker config...`, your override wasn’t found.
4. Once loaded, your scheduled reports and emails should start working as expected.
More details and confirmation of this config loading behavior are in the [official Docker README](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md#L31-L39) and [docker config file](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py#L18-L138).
Let me know if moving your config and restarting fixes the issue!
<!-- 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/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e1d0b739-6ed6-4b3c-a8bb-5eac0a711abb?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Your%20config%20changes%20aren%E2%80%99t%20being%20picked%20up%20because%2C%20in%20Docker%20Compose%2C%20Superset%20only%20loads%20custom%20config%20from%20%60docker/pythonpath_dev/superset_config_docker.py%60%E2%80%94not%20from%20%60superset_config.py%60%20elsewhere.%20This%20is%20why%20your%20alerts/reports%20aren%E2%80%99t%20triggering%2C%20even%20though%20everything%20looks%20correct%20in%20your%20current%20config.%0A%0ATo%20fix%20this%3A%0A1.%20Copy%20your%20custom%20settings%20%28feature%20flags%2C%20CeleryConfig%2C%20SMTP%2C%20Playwright%2C%20etc.%29%20into%20%60docker/pythonpath_dev/superset_config_docker.py%60.%20Use%20%60superset_config_local.example%60%20as%20a%20template%20if%20needed.%0A2.%20Restart%20%28or%20rebuild%29%20all%20Superse
t%20containers.%0A3.%20Check%20your%20container%20logs%20for%20a%20message%20like%20%60Loaded%20your%20Docker%20configuration%20at%20%5B...%5D%60%20to%20confirm%20the%20override%20is%20loaded.%20If%20you%20see%20%60Using%20default%20Docker%20config...%60%2C%20your%20override%20wasn%E2%80%99t%20found.%0A4.%20Once%20loaded%2C%20your%20scheduled%20reports%20and%20emails%20should%20start%20working%20as%20expected.%0A%0AMore%20details%20and%20confirmation%20of%20this%20config%20loading%20behavior%20are%20in%20the%20%5Bofficial%20Docker%20README%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md%23L31-L39%29%20and%20%5Bdocker%20config%20file%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py%23L18-L138%29.%0A%0ALet%20me%20know%20if%20moving%20your%20config%20and%20restarting%20fixes%20the%20issue%21) [](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/issues/37357)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3784038903
<!-- Answer -->
The log message "Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]" means Superset is running with its default Docker config because no custom override was found or loaded. When you created superset_config_docker.py and "superset init" failed, it was likely due to a syntax or import error in that file—Superset only catches ImportError, so any other error will cause startup to fail and show a traceback in the logs[^1][^2].
To safely add custom config, copy docker/pythonpath_dev/superset_config_local.example to docker/pythonpath_dev/superset_config_docker.py and make minimal, syntactically correct changes. Restart your containers and check the logs for "Loaded your Docker configuration at [...]" to confirm it's loaded. If you see an error or "superset init" fails again, please share the contents of your superset_config_docker.py and any error messages from the logs for further help. If you remove superset_config_docker.py, Superset will always fall back to the default config, which is expected[^1][^2][^3].
[^1]: https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py#L18-L139
[^2]: https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md#L31-L51
[^3]: https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config_local.example#L19-L27
<!-- 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/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20log%20message%20%22Loaded%20your%20LOCAL%20configuration%20at%20%5B/app/docker/pythonpath_dev/superset_config.py%5D%22%20means%20Superset%20is%20running%20with%20its%20default%20Docker%20config%20because%20no%20custom%20override%20was%20found%20or%20loaded.%20When%20you%20created%20superset_config_docker.py%20and%20%22superset%20init%22%20failed%2C%20it%20was%20likely%20due%20to%20a%20syntax%20or%20import%20error%20in%20that%20file%E2%80%94Superset%20only%20catches%20ImportError%2C%20so%20any%20other%20error%20will%20cause%20startup%20to%20fail%20and%20show%20a%20traceback%20in%20the%20logs%5B%5E1%5D%5B%5E2%5D.%0A%0ATo%20safely%20add%20custom%20config%2C%20copy%20docker/pythonpath_dev/superset_config_local.example%20to%20docker/pythonpath_dev
/superset_config_docker.py%20and%20make%20minimal%2C%20syntactically%20correct%20changes.%20Restart%20your%20containers%20and%20check%20the%20logs%20for%20%22Loaded%20your%20Docker%20configuration%20at%20%5B...%5D%22%20to%20confirm%20it%27s%20loaded.%20If%20you%20see%20an%20error%20or%20%22superset%20init%22%20fails%20again%2C%20please%20share%20the%20contents%20of%20your%20superset_config_docker.py%20and%20any%20error%20messages%20from%20the%20logs%20for%20further%20help.%20If%20you%20remove%20superset_config_docker.py%2C%20Superset%20will%20always%20fall%20back%20to%20the%20default%20config%2C%20which%20is%20expected%5B%5E1%5D%5B%5E2%5D%5B%5E3%5D.%0A%0A%5B%5E1%5D%3A%20https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py%23L18-L139%0A%5B%5E2%5D%3A%20https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md%23L31-L51%0A%5B%5E3%5D%3A%20https%3A//github.com/apache/superset/
blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config_local.example%23L19-L27) [](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/issues/37357)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3786007470
Hello, this appears to be a Q&A request for help rather than a bug report. I would suggest for starters running an official release docker image like `apache/superset:6.0.0`. I can verify that Alerts & Reports work great with a docker compose deployment and that version, so this is a matter of your configuration rather than a bug in Superset.
Feel free to work with Dosu, there's also the #ask-ai channel in Superset Slack. But I am inclined to convert this to a discussion, though, as it doesn't need to be in our bug tracker.
If, when you get this resolved, you find there's something we should add to the docs, we'd love if you could add it!
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3784452457
Hi Dosu,
I created and ran superset_config_docker.py and applied a few changes based
on the recommendations. Some of the configuration is now being picked up,
but emails are still not being sent.
Thanks,
Hariprasath N
On Thu, 22 Jan 2026 at 17:34, dosubot[bot] ***@***.***> wrote:
> *dosubot[bot]* left a comment (apache/superset#37357)
> <https://github.com/apache/superset/issues/37357#issuecomment-3784038903>
>
> The log message "Loaded your LOCAL configuration at
> [/app/docker/pythonpath_dev/superset_config.py]" means Superset is running
> with its default Docker config because no custom override was found or
> loaded. When you created superset_config_docker.py and "superset init"
> failed, it was likely due to a syntax or import error in that file—Superset
> only catches ImportError, so any other error will cause startup to fail and
> show a traceback in the logs1
> <#m_6287754375601459726_user-content-fn-1-eb7aec38652e96ee25ea2a644e6c6c03>
> 2
> <#m_6287754375601459726_user-content-fn-2-eb7aec38652e96ee25ea2a644e6c6c03>
> .
>
> To safely add custom config, copy
> docker/pythonpath_dev/superset_config_local.example to
> docker/pythonpath_dev/superset_config_docker.py and make minimal,
> syntactically correct changes. Restart your containers and check the logs
> for "Loaded your Docker configuration at [...]" to confirm it's loaded. If
> you see an error or "superset init" fails again, please share the contents
> of your superset_config_docker.py and any error messages from the logs for
> further help. If you remove superset_config_docker.py, Superset will always
> fall back to the default config, which is expected1
> <#m_6287754375601459726_user-content-fn-1-eb7aec38652e96ee25ea2a644e6c6c03>
> 2
> <#m_6287754375601459726_user-content-fn-2-eb7aec38652e96ee25ea2a644e6c6c03>
> 3
> <#m_6287754375601459726_user-content-fn-3-eb7aec38652e96ee25ea2a644e6c6c03>
> .
>
> *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.*
> ------------------------------
>
> How did I do? Good
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=great_response>
> | Irrelevant
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=irrelevant_answer>
> | Incorrect
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=incorrect_sources>
> | Verbose
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=too_verbose>
> | Hallucination
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=hallucination>
> | Report 🐛
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?feedback_type=bug_report>
> | Other
> <https://app.dosu.dev/response-feedback/c7884f1c-65ee-421c-a669-488d22812af5?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=The%20log%20message%20%22Loaded%20your%20LOCAL%20configuration%20at%20%5B/app/docker/pythonpath_dev/superset_config.py%5D%22%20means%20Superset%20is%20running%20with%20its%20default%20Docker%20config%20because%20no%20custom%20override%20was%20found%20or%20loaded.%20When%20you%20created%20superset_config_docker.py%20and%20%22superset%20init%22%20failed%2C%20it%20was%20likely%20due%20to%20a%20syntax%20or%20import%20error%20in%20that%20file%E2%80%94Superset%20only%20catches%20ImportError%2C%20so%20any%20other%20error%20will%20cause%20startup%20to%20fail%20and%20show%20a%20traceback%20in%20the%20logs%5B%5E1%5D%5B%5E2%5D.%0A%0ATo%20safely%20add%20custom%20config%2C%20copy%20docker/pythonpath_dev/superset_config_local.example%20to%20docker/pythonpath_dev/superset_config_docker.py%20and%20make%20minimal%2C%20syntactically%20correct%20changes.%20Restart%20your%20containers%20and%20check%20the%20logs%20for%20%22Loaded%20your%20Docker%20configuration%2
0at%20%5B...%5D%22%20to%20confirm%20it%27s%20loaded.%20If%20you%20see%20an%20error%20or%20%22superset%20init%22%20fails%20again%2C%20please%20share%20the%20contents%20of%20your%20superset_config_docker.py%20and%20any%20error%20messages%20from%20the%20logs%20for%20further%20help.%20If%20you%20remove%20superset_config_docker.py%2C%20Superset%20will%20always%20fall%20back%20to%20the%20default%20config%2C%20which%20is%20expected%5B%5E1%5D%5B%5E2%5D%5B%5E3%5D.%0A%0A%5B%5E1%5D%3A%20https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py%23L18-L139%0A%5B%5E2%5D%3A%20https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md%23L31-L51%0A%5B%5E3%5D%3A%20https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config_local.example%23L19-L27>
> [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>
> Footnotes
>
> 1.
>
>
> https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py#L18-L139
> ↩
> <#m_6287754375601459726_user-content-fnref-1-eb7aec38652e96ee25ea2a644e6c6c03>
> ↩2
> <#m_6287754375601459726_user-content-fnref-1-2-eb7aec38652e96ee25ea2a644e6c6c03>
> 2.
>
>
> https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md#L31-L51
> ↩
> <#m_6287754375601459726_user-content-fnref-2-eb7aec38652e96ee25ea2a644e6c6c03>
> ↩2
> <#m_6287754375601459726_user-content-fnref-2-2-eb7aec38652e96ee25ea2a644e6c6c03>
> 3.
>
>
> https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config_local.example#L19-L27
> ↩
> <#m_6287754375601459726_user-content-fnref-3-eb7aec38652e96ee25ea2a644e6c6c03>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/superset/issues/37357#issuecomment-3784038903>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCNYORXU3JTCZ2FRIBVU5MD4IC4GFAVCNFSM6AAAAACSQNNHUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBUGAZTQOJQGM>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "Hariprasath-0018 (via GitHub)" <gi...@apache.org>.
Hariprasath-0018 commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3784611727
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/supers
et/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:
> ***@***.***>
>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Alerts and Reports Emails Not Sending [superset]
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke commented on issue #37357:
URL: https://github.com/apache/superset/issues/37357#issuecomment-3791349155
Sorry, that's not enough info for me to be able to debug this further. Try the bots in the #ask-ai channel in the Apache Superset Slack. they should be willing to dig in with more info.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org