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_now.py:124

                logger.error("Celery task execution failed: %s", str(celery_ex))
                raise ReportScheduleExecuteNowFailedError() from celery_ex

            return execution_id

        except CommandException:
            raise
        except Exception as ex:
            logger.exception(
                "Unexpected error executing report schedule %d", self._model_id
            )
            raise ReportScheduleExecuteNowFailedError() from ex

    def validate(self) -> None:
        """Validate the report schedule exists and the user has permission to
        execute."""
        self._model = ReportScheduleDAO.find_by_id(self._model_id)
        if not self._model:
            raise ReportScheduleNotFoundError()

        try:
            security_manager.raise_for_editorship(self._model)
        except SupersetSecurityException as ex:
            raise ReportScheduleForbiddenError() from ex

View on GitHub (pinned to f4587218dd)

Solutions

1. Confirm the report schedule ID still exists; it may have been deleted.

When it happens

Trigger: Execute-now is requested for a report schedule that no longer exists.

Common situations: Triggering 'execute now' for a report schedule id that does not exist.

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