From fb2a8ac9a214475ac9f8501b7004b77be927d0da Mon Sep 17 00:00:00 2001 From: Yousuf Ansari <141269047+YousufFFFF@users.noreply.github.com> Date: Wed, 26 Nov 2025 04:14:51 +0530 Subject: [PATCH] docs: clarify duplicate report deliveries for alerts & reports (#36264) Co-authored-by: Evan Rusackas Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/docs/configuration/alerts-reports.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/docs/configuration/alerts-reports.mdx b/docs/docs/configuration/alerts-reports.mdx index e31d4325741..eca5037473b 100644 --- a/docs/docs/configuration/alerts-reports.mdx +++ b/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 schedule them independently). +- Review your deployment/orchestration setup (for example systemd, Docker, or Kubernetes) to make sure the alerts & reports scheduler is **not started from multiple places by accident**. + ## Scheduling Queries as Reports You can optionally allow your users to schedule queries directly in SQL Lab. This is done by adding