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

<!-- Answer -->
The logs you shared show that the scheduler is running, but this only means the 
scheduling mechanism is working. For actual report delivery, you need to see 
logs for the reports.execute task—this is what runs the report, generates 
screenshots, and sends notifications. If you don’t see reports.execute in your 
worker logs after the scheduler runs, reports aren’t being processed.

Here’s what to check next:
- Look for reports.execute tasks and any related errors or warnings in your 
Celery worker logs.
- In the Superset UI or metadata database, check the ReportExecutionLog table 
for recent executions, their states, and any error messages—this often reveals 
silent failures that don’t show up in the UI.
- Make sure the EMAIL_REPORTS_USER (or the user configured for reports) can log 
in and access the dashboards/charts being reported. If this user lacks access, 
report execution will silently fail.
- If you use SSO or custom authentication, confirm that 
MACHINE_AUTH_PROVIDER_CLASS and WEBDRIVER_AUTH_FUNC are set up so background 
tasks can authenticate.
- If all else fails, review your report schedule configuration (recipients, 
schedule, status) and SMTP/notification settings again.

Silent failures are often caused by authentication issues, misconfigured 
dry-run mode, or notification errors that don’t show up as obvious failures in 
the logs. Checking the above should help pinpoint where things are getting 
stuck. For more details, see [this 
discussion](https://github.com/apache/superset/discussions/34943) and [this 
issue](https://github.com/apache/superset/issues/32001).


<!-- 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/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/ba0ce506-d8e3-4232-be36-9325320c15ac?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-14400450

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