You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each triggering of an alert or report appears in the log twice. Once with its actual runtime and result, once with a runtime of 00:00:00 or 00:00:01. Is there a bad join or does some event need to be filtered out?
How to reproduce the bug
Create an alert or report, let it run, look at the execution log.
Screenshots/recordings
Superset version
4.0.2
Python version
I don't know
Node version
I don't know
Browser
Not applicable
Additional context
In case it matters, all reports and alerts are being delivered by email, not Slack.
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.
The text was updated successfully, but these errors were encountered:
Examine the Database Queries:- Review the queries that retrieve the log entries for display. Ensure there are no issues like joins or unions that could be causing duplicate entries.
Sample snippet:-
def log_execution(alert_id, runtime, result):
# This function should only be called once per execution
# Ensure there's no duplicate call to this function
log_entry = {
'alert_id': alert_id,
'runtime': runtime,
'result': result,
}
save_log_entry_to_database(log_entry)
# This function might be called at different stages of execution
# Ensure it’s not causing duplicate log entries
def execute_alert(alert):
start_time = get_current_time()
log_execution(alert.id, start_time, "Started")
result = perform_alert_execution(alert)
end_time = get_current_time()
log_execution(alert.id, end_time, result)
Follow the same for checking the queries
Hope this helps, Thanks
Bug description
Each triggering of an alert or report appears in the log twice. Once with its actual runtime and result, once with a runtime of 00:00:00 or 00:00:01. Is there a bad join or does some event need to be filtered out?
How to reproduce the bug
Create an alert or report, let it run, look at the execution log.
Screenshots/recordings
Superset version
4.0.2
Python version
I don't know
Node version
I don't know
Browser
Not applicable
Additional context
In case it matters, all reports and alerts are being delivered by email, not Slack.
Checklist
The text was updated successfully, but these errors were encountered: