dosubot[bot] commented on issue #35082: URL: https://github.com/apache/superset/issues/35082#issuecomment-3273375195
<!-- Answer --> The most common cause of fatal errors when saving dashboards in Superset master/latest-dev is a version mismatch between the frontend and backend, especially around the handling of color and theme fields like `map_label_colors` and `shared_label_colors`. If these fields are missing or have the wrong type in the dashboard metadata, the backend will reject the save with a 400/422 error, which surfaces as a generic "fatal error" in the UI. This can also happen if recent changes to dashboard or theme handling introduced stricter validation or new required fields that older dashboards or charts don't satisfy ([example](https://github.com/apache/superset/issues/31397), [example](https://github.com/apache/superset/issues/33015)). To troubleshoot: - Double-check that both your frontend and backend are running the exact same Superset version. Even a small mismatch can cause these payload/schema errors. - Inspect the dashboard and chart metadata for invalid or missing `map_label_colors` or `shared_label_colors`. If you see errors about "Unknown field" or "Not a valid mapping type", try editing the affected chart, go to the "Advanced" section, and remove or correct the problematic color fields ([details](https://github.com/apache/superset/issues/32784)). - If you recently imported dashboards or upgraded, re-save any charts that are part of the dashboard to ensure their metadata and query context are up to date ([details](https://github.com/apache/superset/issues/33615)). - Check your backend logs for validation errors or stacktraces when the save fails—these often include the exact field or schema problem. If the issue persists, sharing the backend error log or the failing dashboard/chart metadata will help pinpoint the root cause. Recent changes to theme import/export logic could also affect dashboard saves if themes are involved ([PR #34850](https://github.com/apache/superset/pull/34850)). <!-- 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/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5b1a957c-f98a-41ee-81c2-9195e23e20a9?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](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/35082) -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
