apache/superset · error · NotificationParamException
Invalid Slack recipient configuration
Error message
Invalid Slack recipient configuration
What it means
Error "Invalid Slack recipient configuration" thrown in apache/superset.
Source
Thrown at superset/commands/report/slack_upgrade.py:104
recipient,
recipient_type,
recipient_config_json,
) in self._upgraded_recipient_state:
recipient.type = recipient_type
recipient.recipient_config_json = recipient_config_json
self._upgraded_recipient_state = []
def update_recipients(self) -> None:
"""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
)View on GitHub (pinned to f4587218dd)
Solutions
- Fix the Slack recipient list: use valid channel/user targets for the v2 Slack API.
- Ensure the Slack bot token and scopes are configured correctly.
When it happens
Trigger: The stored Slack recipients cannot be mapped to valid v2 Slack targets during upgrade.
Common situations: Upgrading Slack recipients to v2 when the stored recipient config is malformed (missing channel/user id).
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/75d344b43c046533.
Report an issue: GitHub.