Copilot commented on code in PR #36264: URL: https://github.com/apache/superset/pull/36264#discussion_r2561166406
########## docs/docs/configuration/alerts-reports.mdx: ########## @@ -294,6 +294,14 @@ Check this by attempting to `curl` the URL of a report that you see in the error In a deployment with authentication measures enabled like HTTPS and Single Sign-On, it may make sense to have the worker navigate directly to the Superset application running in the same location, avoiding the need to sign in. For instance, you could use `WEBDRIVER_BASEURL="http://superset_app:8088"` for a docker compose deployment, and set `"force_https": False,` in your `TALISMAN_CONFIG`. +### Duplicate report deliveries + +In some deployment configurations a scheduled report can be delivered more than once around its planned time. This typically happens when more than one process is responsible for running the alerts & reports schedule (for example, multiple schedulers or Celery beat instances). To avoid duplicate emails or notifications: + +- Ensure that only a **single scheduler/beat process** is configured to trigger alerts and reports for a given environment. +- If you run **multiple Celery workers**, verify that there is still only one component responsible for scheduling the report tasks (workers should execute tasks, not independently schedule them). Review Comment: [nitpick] The parenthetical clarification uses 'independently schedule them' which could be more precise. Consider: 'workers should execute tasks, not schedule them independently' to maintain parallel structure with the main clause. ```suggestion - If you run **multiple Celery workers**, verify that there is still only one component responsible for scheduling the report tasks (workers should execute tasks, not schedule them independently). ``` -- 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]
