apache/superset · error · ReportScheduleSystemErrorsException
Report schedule system error
Error message
Report schedule system error
What it means
Error "Report schedule system error" thrown in apache/superset.
Source
Thrown at superset/commands/report/execute.py:1402
error_type=SupersetErrorType.REPORT_NOTIFICATION_ERROR,
level=(
ErrorLevel.ERROR if ex.status >= 500 else ErrorLevel.WARNING
),
)
)
except Exception:
if self._slack_v1_upgrade.is_upgraded_recipient(recipient):
self._slack_v1_upgrade.restore_upgraded_recipients()
raise
if upgraded_delivery_failed:
self._slack_v1_upgrade.restore_upgraded_recipients()
if notification_errors:
# log all errors but raise based on the most severe
for error in notification_errors:
logger.warning(str(error))
if any(error.level == ErrorLevel.ERROR for error in notification_errors):
raise ReportScheduleSystemErrorsException(errors=notification_errors)
if any(error.level == ErrorLevel.WARNING for error in notification_errors):
raise ReportScheduleClientErrorsException(errors=notification_errors)
def send(self) -> None:
"""
Creates the notification content and sends them to all recipients
:raises: CommandException
"""
notification_content = self._get_notification_content()
self._send(notification_content, self._report_schedule.recipients)
def send_error(self, name: str, message: str) -> None:
"""
Creates and sends a notification for an error, to all recipients
:raises: CommandException
"""View on GitHub (pinned to f4587218dd)
Solutions
- Check Celery worker and Superset logs for the system error and retry the schedule once resolved.
When it happens
Trigger: A system-level failure occurs while executing a report schedule.
Common situations: Report execution fails with an internal/server-side exception (screenshot service down, worker crash).
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/b23fcb3567a358c2.
Report an issue: GitHub.