dosubot[bot] commented on issue #37282: URL: https://github.com/apache/superset/issues/37282#issuecomment-3772218665
<!-- Greeting --> Hi @victor-cherescu! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> There are a few known causes for dashboards getting stuck on loading after upgrading to Superset 6.0.0, even when charts load fine directly and no errors appear: - If you have the DYNAMIC_PLUGINS feature flag enabled in your superset_config.py, disable it. This beta feature is known to cause dashboards to hang indefinitely in 6.0.0 and leads to missing endpoints and UI loading issues. Disabling it resolves the problem [details](https://github.com/apache/superset/issues/36211). - Superset 6.0.0+ requires Node.js 20.x for frontend builds. Using Node 16 or 18 can cause missing assets and subtle UI failures, including dashboards not rendering [details](https://github.com/apache/superset/issues/36940). - After upgrading and rebuilding assets, clear your browser cache and localStorage. Stale frontend assets or cached theme data can block dashboard rendering [details](https://github.com/apache/superset/issues/36940). - If your dashboards use custom themes, check for metadata schema mismatches (e.g., `theme_id` vs `theme_uuid`). There were changes in dashboard theming metadata in the 6.0.0 release cycle, and schema mismatches can cause dashboards to fail to load without visible errors [details](https://github.com/apache/superset/issues/35177). - If your dashboards have nested tabs and you use the manual "Refresh dashboard" button, there is a known bug in 6.0.0 that causes an infinite loading loop. As a workaround, avoid manual refresh on dashboards with nested tabs, use auto-refresh, or temporarily restructure dashboards to remove nested tabs [details](https://github.com/apache/superset/issues/37093). If none of these apply, inspect the API responses for `/api/v1/dashboard/{id}/`, `/charts`, and `/datasets` for missing or malformed fields (especially `position_json`, `json_metadata`, and theme fields). Enabling debug logging on both backend and frontend may also reveal hidden errors during dashboard load. Let me know if any of these steps help or if you find anything unusual in the API responses! <!-- 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/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d54d7e59-6ac9-47f4-95c9-d4d4ebd6fc65?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=There%20are%20a%20few%20known%20causes%20for%20dashboards%20getting%20stuck%20on%20loading%20after%20upgrading%20to%20Superset%206.0.0%2C%20even%20when%20charts%20load%20fine%20directly%20and%20no%20errors%20appear%3A%0A%0A-%20If%20you%20have%20the%20DYNAMIC_PLUGINS%20feature%20flag%20enabled%20in%20your%20superset_config.py%2C%20disable%20it.%20This%20beta%20feature%20is%20known%20to%20cause%20dashboards%20to%20hang%20indefinitely%20in%206.0.0%20and%20leads%20to%20missing%20endpoints%20and%20UI%20loading%20issues.%20Disabling%20it%20resolves%20the%20problem%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/36211%29.%0A-%20Superset%206.0.0%2B%20requires%20Node.js%2020.x%20for%20frontend%20builds.%20Using%20Node%2016%20or%2018%20can%2 0cause%20missing%20assets%20and%20subtle%20UI%20failures%2C%20including%20dashboards%20not%20rendering%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/36940%29.%0A-%20After%20upgrading%20and%20rebuilding%20assets%2C%20clear%20your%20browser%20cache%20and%20localStorage.%20Stale%20frontend%20assets%20or%20cached%20theme%20data%20can%20block%20dashboard%20rendering%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/36940%29.%0A-%20If%20your%20dashboards%20use%20custom%20themes%2C%20check%20for%20metadata%20schema%20mismatches%20%28e.g.%2C%20%60theme_id%60%20vs%20%60theme_uuid%60%29.%20There%20were%20changes%20in%20dashboard%20theming%20metadata%20in%20the%206.0.0%20release%20cycle%2C%20and%20schema%20mismatches%20can%20cause%20dashboards%20to%20fail%20to%20load%20without%20visible%20errors%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/35177%29.%0A-%20If%20your%20dashboards%20have%20nested%20tabs%20and%20you%20use%20the%20manual%20%22Re fresh%20dashboard%22%20button%2C%20there%20is%20a%20known%20bug%20in%206.0.0%20that%20causes%20an%20infinite%20loading%20loop.%20As%20a%20workaround%2C%20avoid%20manual%20refresh%20on%20dashboards%20with%20nested%20tabs%2C%20use%20auto-refresh%2C%20or%20temporarily%20restructure%20dashboards%20to%20remove%20nested%20tabs%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/37093%29.%0A%0AIf%20none%20of%20these%20apply%2C%20inspect%20the%20API%20responses%20for%20%60/api/v1/dashboard/%7Bid%7D/%60%2C%20%60/charts%60%2C%20and%20%60/datasets%60%20for%20missing%20or%20malformed%20fields%20%28especially%20%60position_json%60%2C%20%60json_metadata%60%2C%20and%20theme%20fields%29.%20Enabling%20debug%20logging%20on%20both%20backend%20and%20frontend%20may%20also%20reveal%20hidden%20errors%20during%20dashboard%20load.%0A%0ALet%20me%20know%20if%20any%20of%20these%20steps%20help%20or%20if%20you%20find%20anything%20unusual%20in%20the%20API%20responses%21) [](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/37282) -- 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]
