apache/superset · error · ReportScheduleNotFoundError

Report Schedule not found.

Error message

Report Schedule not found.

What it means

Error "Report Schedule not found." thrown in apache/superset.

Source

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

                    self._execution_id,
                    str(ex) or type(ex).__name__,
                    type(ex).__name__,
                    report_execution_context,
                )
            raise ReportScheduleUnexpectedError(str(ex)) from ex

    def validate(self) -> None:
        # Validate/populate model exists
        logger.info(
            "session is validated: id %s, executionid: %s",
            self._model_id,
            self._execution_id,
        )
        self._model = (
            db.session.query(ReportSchedule).filter_by(id=self._model_id).one_or_none()
        )
        if not self._model:
            raise ReportScheduleNotFoundError()

View on GitHub (pinned to f4587218dd)

Solutions

1. Confirm the report schedule ID still exists; it may have been deleted.
2. List schedules via GET /api/v1/report/ to find the correct ID.

When it happens

Trigger: Looking up a report schedule that no longer exists.

Common situations: Executing a report schedule that no longer exists (deleted after the task was queued).

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