Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to update slack recipients to v2 #31936

Open
3 tasks done
iercan opened this issue Jan 21, 2025 · 3 comments
Open
3 tasks done

Failed to update slack recipients to v2 #31936

iercan opened this issue Jan 21, 2025 · 3 comments
Labels
alert-reports Namespace | Anything related to the Alert & Reports feature

Comments

@iercan
Copy link
Contributor

iercan commented Jan 21, 2025

Bug description

I upgraded Superset to 4.1.1 and attempted to migrate the Slack API due to the old version being deprecated. However, the new version isn't functioning properly. The logs show an error, and while old reports and alerts work fine, the new version seems unable to upgrade or send reports.

I've already added channels:read scope. There is no problem to adding new alert.

superset-worker-1  | [2025-01-21 05:55:13,723: INFO/MainProcess] Slack API v2 is available
superset-worker-1  | [2025-01-21 05:55:13,723: INFO/MainProcess] Attempting to upgrade the report to Slackv2: Report should not be run with the Slack V1 api.
superset-worker-1  |     Attempting to run with V2 if required Slack scopes are available
superset-worker-1  | [2025-01-21 05:55:15,462: WARNING/MainProcess] Failed to update slack recipients to v2: No recipients saved in the report

Screenshots/recordings

No response

Superset version

4.1.1

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Copy link

dosubot bot commented Jan 21, 2025

The error message "No recipients saved in the report" indicates that the _get_channels method is returning an empty list, meaning no recipient channels were found or specified in the report configuration. This results in a NotificationParamException being raised [1].

To resolve this issue, ensure that the report configuration includes valid recipient channels. You may need to verify that the necessary Slack scopes are correctly configured for the Slack API v2 integration. The required Slack scopes are incoming-webhook, files:write, chat:write, channels:read, and groups:read [2][3]. Make sure these scopes are granted to your Slack app to allow proper functionality with the v2 API.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot dosubot bot added the alert-reports Namespace | Anything related to the Alert & Reports feature label Jan 21, 2025
@iercan
Copy link
Contributor Author

iercan commented Jan 21, 2025

@dosu I've already add required scopes. There is no problem with updating or adding new alerts from web ui. After I updated alerts, It is able to send reports.

Copy link

dosubot bot commented Jan 21, 2025

@iercan, I'm just a bot here to help with bugs, technical questions, and engineering knowledge. It sounds like your issue might be resolved if the reports are sending after updating alerts. If there's something else you need help with, feel free to ask! If you think I should have addressed something specific, you can always reach out to the Dosu Team.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert-reports Namespace | Anything related to the Alert & Reports feature
Projects
None yet
Development

No branches or pull requests

1 participant