apache/superset · error · ReportScheduleExecuteNowFailedError
Report Schedule execute now failed.
Error message
Report Schedule execute now failed.
What it means
Error "Report Schedule execute now failed." thrown in apache/superset.
Source
Thrown at superset/commands/report/execute_now.py:72
self._model: Optional[ReportSchedule] = None
def run(self) -> str:
"""
Execute the command and return an execution UUID for tracking.
Returns:
str: Execution UUID that can be used to track the execution status.
Raises:
ReportScheduleNotFoundError: Report schedule not found.
ReportScheduleForbiddenError: User doesn't have permission to execute.
ReportScheduleCeleryNotConfiguredError: Celery broker is not reachable.
ReportScheduleExecuteNowFailedError: Execution failed to start.
"""
try:
self.validate()
if not self._model:
raise ReportScheduleExecuteNowFailedError()
execution_id = str(uuid4())
logger.info(
"Manually executing report schedule %s (id: %d), execution_id: %s",
self._model.name,
self._model.id,
execution_id,
)
# Import here to avoid circular imports
from superset.tasks.scheduler import execute
# Set eta to now so the downstream task receives a valid scheduled_dttm.
async_options: dict[str, Any] = {
"task_id": execution_id,
"eta": datetime.now(tz=timezone.utc),
}View on GitHub (pinned to f4587218dd)
Solutions
- Check worker logs for the failure, fix the underlying issue, and retry the execute-now request.
When it happens
Trigger: The execute-now task for a report schedule fails.
Common situations: Triggering 'execute now' on a report schedule when the Celery task dispatch or execution fails.
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/1b005c3f66b93c2d.
Report an issue: GitHub.