There is no error in any log, but report is not sent for both slack and email.

[lyric2249]

Bug description

We are currently using Superset latest (4.1.1), and imac. After cloning the repository via Git (https://github.com/apache/superset), we set up the Superset environment using docker-compose-image-tag.yml with Docker Compose. To investigate an issue, we modified docker-compose-image-tag.yml to add a Flower container.

After setting up the reports, we attempted to send them. Although all the report dispatches show as "success," none of the reports are being delivered. We checked all the logs, including those for worker, worker-beat, Flower, and web, and they all indicate that the dispatches were successful.

The configuration is set as follows:

• ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
• "ALERT_REPORTS": True
• "ALERT_REPORT_SLACK_V2": True

SMTP is configured with Gmail, and SLACK_API_TOKEN is set as "xoxb-......". When setting up SMTP, I used an app password generated by Google. Additionally, when I tested the email example code provided in the Alert & Report section of the Superset documentation (https://superset.apache.org/docs/configuration/alerts-reports/#send-a-test-email) with my Gmail information, the email was successfully sent.

I cannot figure out why the reports are not being delivered. Could you help me understand why this issue occurs?

Screenshots/recordings

• docker containers

• worker logs

• flower logs

• report execution logs

• report configuration

Superset version

master / latest-dev

Python version

3.10

Node version

I don't know

Browser

Safari

Additional context

No response

Checklist

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

[dosubot]

Hey there, @lyric2249! I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this together!

I found some similar discussions that might be relevant to your issue:

1. Nothing triggered issue in alert report in superset - This discussion is still open and might provide insights into similar problems with alert reports not being triggered ^[1].

2. No Slack notification method when using Report/Alert and Docker Compose - This discussion is also open and addresses issues with Slack notifications in a Docker Compose setup ^[2].

3. Alerting mechanism of apache superset does not work at all - This is another open discussion that might have relevant information about alerting mechanisms not functioning as expected ^[3].

Regarding your issue, ensure that the ALERT_REPORTS_NOTIFICATION_DRY_RUN is set to False, which you have already done. Additionally, verify that the SLACK_API_TOKEN is correctly configured and not empty, as an empty token would prevent Slack notifications from being sent ^[2].

Since your SMTP configuration seems correct (as test emails are sent successfully), and the logs indicate success, it might be worth checking the network and authentication settings to ensure the worker can access the report URL. You can use curl to test the URL from the worker environment and adjust WEBDRIVER_BASEURL if necessary ^[4].

If the issue persists, reviewing the Celery worker logs for any discrepancies in task execution might provide further insights ^[4].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[iercan]

The worker logs indicate that ALERT_REPORTS_NOTIFICATION_DRY_RUN is enabled. Please verify your configuration.

[lyric2249]

Thank you for the notification. When I set ALERT_REPORTS_NOTIFICATION_DRY_RUN = False in superset/config.py, it appears to work correctly now. However, in docker/pythonpath_dev/superset_config.py, the setting was ALERT_REPORTS_NOTIFICATION_DRY_RUN = False, and I am not sure why it functioned under the configuration ALERT_REPORTS_NOTIFICATION_DRY_RUN = True. For anyone who encounters this issue in the future, please try to fix your superset/config.py file as well.