GitHub user dosubot[bot] added a comment to the discussion: Alerts & reports 
nothing triggered

<!-- Answer -->
Here are some key troubleshooting steps for Superset alerts and reports not 
triggering:

1. Make sure your superset_config.py includes the required CeleryConfig 
beat_schedule settings. You need to schedule the `reports.scheduler` task to 
run every minute and the `reports.prune_log` task daily at 00:10. Without this, 
scheduled alerts and reports won't run as expected. Example config:
```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),
        },
    }
```
See details [here](https://github.com/apache/superset/discussions/31647).

2. Double-check that the environment variable 
`ALERT_REPORTS_NOTIFICATION_DRY_RUN` is set to `False` in your worker 
container. If this is enabled (even if set to False in your config but True in 
the environment), reports will show as dispatched in logs but won't actually be 
delivered. This is a common pitfall—verify both your config and your container 
environment variables. More info 
[here](https://github.com/apache/superset/issues/32001).

3. Check your Superset, Celery worker, and beat logs for any errors or skipped 
tasks related to alerts/reports. Sometimes issues are logged but not surfaced 
in the UI.

4. Review your alert/report configuration in the Superset UI—ensure the 
schedule, recipients, and status are set up correctly.

If these steps don’t resolve the issue, let me know what you find in the logs 
or config, and I can help dig deeper!


<!-- 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/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/fd21765e-137f-4c10-aa4f-da5060061080?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
 nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35138)

GitHub link: 
https://github.com/apache/superset/discussions/35138#discussioncomment-14400023

----
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]

Reply via email to