dosubot[bot] commented on issue #37584: URL: https://github.com/apache/superset/issues/37584#issuecomment-3825618771
<!-- Greeting --> Hi @saulojb! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team. <!-- Answer --> This is a known bug in Superset 6.0.0: dashboards with nested tabs can enter an infinite rerender loop and cause repeated chart request cancellations (NS_BINDING_ABORTED) when you use the manual "Force Refresh" button. Auto-refresh works fine because it uses a different code path. The root cause is a frontend issue with how refreshes are dispatched for nested tabs. A fix was merged on 2026-01-10 ([PR #37018](https://github.com/apache/superset/pull/37018)), which adds a "lazy" refresh option and prevents the infinite loop by tracking handled refreshes in nested tabs. This fix is available in the master/latest-dev branch after that date and will be included in the next release (6.0.1 or later)[source](https://github.com/apache/superset/issues/37093). To resolve the issue, update your deployment to a commit after 2026-01-10 or wait for the next official release. As a workaround, avoid using manual refresh on dashboards with nested tabs, use auto-refresh instead, or temporarily restructure dashboards to remove nested tabs[source](https://github.com/apache/superset/issues/37282). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/51c016bd-6dde-437d-84d9-297eb51dd4c5?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20bug%20in%20Superset%206.0.0%3A%20dashboards%20with%20nested%20tabs%20can%20enter%20an%20infinite%20rerender%20loop%20and%20cause%20repeated%20chart%20request%20cancellations%20%28NS_BINDING_ABORTED%29%20when%20you%20use%20the%20manual%20%22Force%20Refresh%22%20button.%20Auto-refresh%20works%20fine%20because%20it%20uses%20a%20different%20code%20path.%20The%20root%20cause%20is%20a%20frontend%20issue%20with%20how%20refreshes%20are%20dispatched%20for%20nested%20tabs.%0A%0AA%20fix%20was%20merged%20on%202026-01-10%20%28%5BPR%20%2337018%5D%28https%3A//github.com/apache/superset/pull/37018%29%29%2C%20which%20adds%20a%20%22lazy%22%20refresh%20option%20and%20prevents%20the%20infinite%20loop%20by%20tracking%20handled%20refreshes%20in%2 0nested%20tabs.%20This%20fix%20is%20available%20in%20the%20master/latest-dev%20branch%20after%20that%20date%20and%20will%20be%20included%20in%20the%20next%20release%20%286.0.1%20or%20later%29%5Bsource%5D%28https%3A//github.com/apache/superset/issues/37093%29.%0A%0ATo%20resolve%20the%20issue%2C%20update%20your%20deployment%20to%20a%20commit%20after%202026-01-10%20or%20wait%20for%20the%20next%20official%20release.%20As%20a%20workaround%2C%20avoid%20using%20manual%20refresh%20on%20dashboards%20with%20nested%20tabs%2C%20use%20auto-refresh%20instead%2C%20or%20temporarily%20restructure%20dashboards%20to%20remove%20nested%20tabs%5Bsource%5D%28https%3A//github.com/apache/superset/issues/37282%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A //github.com/apache/superset/issues/37584) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
