GitHub user bug-coder-007 created a discussion: Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success'
In Superset 4.1.2, when a Report or Alert is executed for the first time after creation, two execution log entries are generated with the same UUID (Execution ID). For example: Execution ID | Scheduled at (UTC) | Start at (UTC) | Duration | State 696d3e | 2025-10-14 18:52:00 | 2025-10-15 02:52:00 | 00:00:00.000 | success 696d3e | 2025-10-14 18:52:00 | 2025-10-15 02:52:00 | 00:00:00.000 | working As shown, both records have: The same Execution ID (696d3e) Identical scheduled and start timestamps No duration One in success state, one in working state However, only one successful execution log is expected, as this duplication causes confusion and affects downstream log processing. This issue occurs consistently during the first execution of a newly created or updated Report/Alert. Subsequent executions may not show this behavior, or appear less frequently. Environment: Superset version: 4.1.2 Python version: 3.10 OS: Ubuntu Deployment: Standalone (Celery + Gunicorn) Could this be related to a race condition in task scheduling or state update logic? Is there a known fix or workaround? Thanks! @dosu GitHub link: https://github.com/apache/superset/discussions/35658 ---- 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]
