apache/superset · error · NotificationParamException
No recipients saved in the report
Error message
No recipients saved in the report
What it means
Error "No recipients saved in the report" thrown in apache/superset.
Source
Thrown at superset/commands/report/slack_upgrade.py:113
"""Resolve and atomically convert every Slack v1 recipient to Slack v2."""
pending: list[tuple[ReportRecipients, list[str]]] = []
try:
for recipient in self._report_schedule.recipients:
if recipient.type != ReportRecipientType.SLACK:
continue
try:
slack_recipients = json.loads(recipient.recipient_config_json)
except (TypeError, ValueError) as ex:
raise NotificationParamException(
"Invalid Slack recipient configuration"
) from ex
target = (
slack_recipients.get("target")
if isinstance(slack_recipients, dict)
else None
)
if not isinstance(target, str):
raise NotificationParamException(NO_SLACK_RECIPIENTS_MESSAGE)
channels = parse_slack_recipient_targets(target.replace("#", ""))
if not channels:
raise NotificationParamException(NO_SLACK_RECIPIENTS_MESSAGE)
pending.append((recipient, channels))
all_targets = list(
dict.fromkeys(
channel for _, channels in pending for channel in channels
)
)
channel_ids = resolve_slack_channel_ids(all_targets) if all_targets else {}
resolved = [
(
recipient,
json.dumps(
{
"target": ",".join(
channel_ids[channel] for channel in channelsView on GitHub (pinned to f4587218dd)
Solutions
- Add at least one Slack recipient to the report schedule before upgrading or sending.
When it happens
Trigger: Slack upgrade runs against a report with no saved recipients.
Common situations: Upgrading Slack recipients for a report that has no recipient entries stored.
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/af6cdfbcc416d1ec.
Report an issue: GitHub.