You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "bug-coder-007 (via GitHub)" <gi...@apache.org> on 2025/10/15 07:59:02 UTC
[D] Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success' [superset]
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 notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success' [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success'
<!-- Answer -->
This behavior is caused by the state machine logic in Superset: each state transition (like 'working' and then 'success') creates a new execution log entry with the same UUID, scheduled time, and start time, but a different state. There’s no deduplication or update logic—each transition inserts a new row, which can result in duplicate entries if the state machine runs more than once for the same execution. This is not documented as a known issue, and there’s no fix or workaround in 4.1.2. You could potentially mitigate this by adding a uniqueness constraint on the execution UUID or updating the log creation logic to upsert rather than always insert new rows. For more details, see the relevant code in the report execution command and state classes ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py)).
<!-- 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/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ad1c8b08-1dff-447e-8cf6-8f48669d9127?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35658)
GitHub link: https://github.com/apache/superset/discussions/35658#discussioncomment-14684398
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success' [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Duplicate Report/Alert Execution Logs with Same UUID in Superset 4.1.2: One with 'working', One with 'success'
<!-- Answer -->
This behavior is caused by the state machine logic in Superset: each state transition (like 'working' and then 'success') creates a new execution log entry with the same UUID, scheduled time, and start time, but a different state. There’s no deduplication or update logic—each transition inserts a new row, which can result in duplicate entries if the state machine runs more than once for the same execution. This is not documented as a known issue, and there’s no fix or workaround in 4.1.2. You could potentially mitigate this by adding a uniqueness constraint on the execution UUID or updating the log creation logic to upsert rather than always insert new rows. For more details, see the relevant code in the report execution command and state classes ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=ad1c8b08-1dff-447e-8cf6-8f48669d9127) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35658#discussioncomment-14684398
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org