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
Unable to save report due to Add button not enable #28149
Comments
Same issue happening to me. It looks like there is bug in new superset 4.0 version. |
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. |
please contact me if further information is needed , i`m also seeing this bug on my side |
Looking into this. |
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: