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

auto refresh interval won't be updated #17107

Closed
3 tasks done
yougyoung94 opened this issue Oct 14, 2021 · 0 comments · Fixed by #17112
Closed
3 tasks done

auto refresh interval won't be updated #17107

yougyoung94 opened this issue Oct 14, 2021 · 0 comments · Fixed by #17112
Labels
#bug Bug report

Comments

@yougyoung94
Copy link
Contributor

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Click a dashboard
  2. Set auto refresh interval: check the dashboard is refreshing at the right interval
  3. Check out to dashboard list
  4. Go to the dashboard again: check the dashboard won't refresh

Expected results

When you go back to the dashboard, the dashboard should refresh at the right interval

Actual results

When you go back to the dashboard, the dashboard won't refresh at all
what actually happens.

Screenshots

Screen.Recording.2021-10-14.at.12.07.54.PM.mov

Environment

(please complete the following information):

  • browser type and version: Chrome
  • superset version: 1.3.1
  • python version: python --version Python 3.7.9
  • node.js version: node -v v16.4.0
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant