apache/superset · error · ReportScheduleExecuteUnexpectedError

Report Schedule execution got an unexpected error.

Error message

Report Schedule execution got an unexpected error.

What it means

Error "Report Schedule execution got an unexpected error." thrown in apache/superset.

Source

Thrown at superset/commands/report/execute.py:2059

    Execute all types of report schedules.
    - On reports takes chart or dashboard screenshots and sends configured notifications
    - On Alerts uses related Command AlertCommand and sends configured notifications
    """

    def __init__(self, task_id: str, model_id: int, scheduled_dttm: datetime):
        self._model_id = model_id
        self._model: Optional[ReportSchedule] = None
        self._scheduled_dttm = scheduled_dttm
        self._execution_id = UUID(task_id)

    def run(self) -> None:
        monotonic_started_at = time.monotonic()
        report_execution_context: ReportExecutionContext | None = None
        owns_report_working_state = False
        try:
            self.validate()
            if not self._model:
                raise ReportScheduleExecuteUnexpectedError()

            if self._model.type == ReportScheduleType.REPORT:
                # An invocation that enters on WORKING is a duplicate or stale
                # recovery, not the owner that created the active row. Its state
                # handler may terminalize a stale execution, but the command
                # boundary must never infer ownership from a replayed UUID.
                owns_report_working_state = (
                    self._model.last_state != ReportState.WORKING
                )
                total_seconds = resolve_report_execution_budget_seconds(
                    app.config,
                    working_timeout=self._model.working_timeout,
                )
                deadline = ReportExecutionDeadline(
                    total_seconds=total_seconds,
                    started_at=monotonic_started_at,
                )
                dashboard = self._model.dashboard

View on GitHub (pinned to f4587218dd)

Solutions

1. Inspect worker logs for the unexpected exception and retry the schedule after resolving it.

When it happens

Trigger: An unhandled exception interrupts report schedule execution.

Common situations: Report schedule run hits an unhandled exception outside the known timeout/screenshot/data paths.

AI-assisted analysis of apache/superset@f4587218dd (2026-08-14). Data as JSON: /api/errors/8b64e3421ac11006. Report an issue: GitHub.