You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While filling in all the required information there is still an error in the Notification method section where it shows that a recipient is missing even when valid emails are provided.
How to reproduce the bug
Go to alerts and reports.
Go to the report section
Click Add report
Fill all required fields.
What should happen:
The ADD button is enabled and the report can be saved
What is happening:
The ADD button is not enabled and a red asterisk is shown in the EMAIL RECIPIENTS field.
Screenshots/recordings
Superset version
master / latest-dev
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.
The text was updated successfully, but these errors were encountered:
Someone in Slack is seeing this too. I am running 4.0.0 in production and can successfully create a new alert, so this is not universally broken. My best guess is that there's something in the recipients validation checker that succeeds on my instance but fails for these people without telling them why. CC @fisjac as I believe they wrote some of this new validation.
Bug description
While filling in all the required information there is still an error in the Notification method section where it shows that a recipient is missing even when valid emails are provided.
How to reproduce the bug
What should happen:
What is happening:
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: