bito-code-review[bot] commented on PR #35800:
URL: https://github.com/apache/superset/pull/35800#issuecomment-3433326321
<details open>
<summary><strong>Interaction Diagram by <a
href="https://bito.ai#sequence_diagram";>Bito</a></strong></summary>
```mermaid
sequenceDiagram
participant SCHED as Scheduler Task
participant CMD as AsyncExecuteReportScheduleCommand
participant STATE as ReportNotTriggeredErrorState<br/>🔄 Updated | ●●● High
participant BASE as BaseReportState<br/>🔄 Updated | ●●● High
participant DB as Database Session
participant LOG as ReportExecutionLog
Note over STATE, BASE: Enhanced error handling<br/>for concurrent
modifications
SCHED->>CMD: execute_async(task_id, schedule_id)
CMD->>STATE: next() - process report
STATE->>STATE: send() report/alert
STATE->>BASE: update_report_schedule_and_log()
BASE->>LOG: create ReportExecutionLog
BASE->>DB: session.add(log) & commit
DB-->>BASE: StaleDataError (concurrent mod)
BASE->>BASE: rollback & raise ReportScheduleUnexpectedError
BASE-->>STATE: propagate exception
STATE-->>SCHED: ReportScheduleUnexpectedError handled
```
Critical path: Scheduler
Task->AsyncExecuteReportScheduleCommand->ReportNotTriggeredErrorState->BaseReportState->Database
Session
> **Note:** The report execution logging now handles StaleDataError
exceptions when concurrent processes modify or delete report schedules during
execution. This prevents cascading failures by catching database concurrency
issues and raising specific ReportScheduleUnexpectedError exceptions that the
scheduler can handle appropriately.
</details>
--
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]
