apache/superset · error · ReportScheduleStateNotFoundError
Report Schedule state not found
Error message
Report Schedule state not found
What it means
Error "Report Schedule state not found" thrown in apache/superset.
Source
Thrown at superset/commands/report/execute.py:2036
self._report_schedule = report_schedule
self._scheduled_dttm = scheduled_dttm
self._report_execution_context = report_execution_context
@transaction()
def run(self) -> None:
for state_cls in self.states_cls:
if (self._report_schedule.last_state is None and state_cls.initial) or (
self._report_schedule.last_state in state_cls.current_states
):
state_cls(
self._report_schedule,
self._scheduled_dttm,
self._execution_id,
self._report_execution_context,
).next()
break
else:
raise ReportScheduleStateNotFoundError()
class AsyncExecuteReportScheduleCommand(BaseCommand):
"""
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 = NoneView on GitHub (pinned to f4587218dd)
Solutions
- Recreate the report schedule; its log/state row is missing.
- Check for manual deletions in the report_execution_log table.
When it happens
Trigger: The stored state row for a report schedule execution cannot be found.
Common situations: Report execution cannot load its schedule row — deleted or locked by another worker mid-run.
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/55a0362095bfc90e.
Report an issue: GitHub.