apache/superset · error · ReportScheduleClientErrorsException
Report schedule client error
Error message
Report schedule client error
What it means
Error "Report schedule client error" thrown in apache/superset.
Source
Thrown at superset/commands/report/execute.py:1404
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
"""
header_data = self._get_log_data()
url = self._get_url(user_friendly=True)View on GitHub (pinned to f4587218dd)
Solutions
- Review the client error detail in the report logs (e.g., email/Slack delivery failure) and fix the notification configuration.
When it happens
Trigger: A client-side delivery error occurs while sending a report.
Common situations: Report execution fails due to a client-side/config error such as an invalid schedule or missing resource.
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/99caf3211cf4445b.
Report an issue: GitHub.