dosubot[bot] commented on issue #33839:
URL: https://github.com/apache/superset/issues/33839#issuecomment-2990253207

   <!-- Answer -->
   In Superset 4.1.1, if changing the dashboard color scheme doesn't update the 
charts—even with no custom label color settings and both frontend/backend on 
the same version—the most likely cause is stale dashboard state or cached chart 
data. Superset caches chart form data and only refreshes it if it detects a 
change in dashboard metadata or filters. Sometimes, this cache doesn't 
invalidate properly, so charts keep using the old color scheme even after you 
change it in the dashboard settings. A normal browser refresh won't always 
clear this cache.
   
   Try these steps:
   1. After changing the dashboard color scheme, force a hard reload 
(Ctrl+Shift+R or Cmd+Shift+R) and, if possible, clear your browser cache.
   2. Edit and re-save the dashboard (even without changes) to trigger a 
metadata update.
   3. If the issue persists, try editing and saving each affected chart 
individually, then reload the dashboard.
   
   If none of these work, this is a known limitation in 4.1.1's color scheme 
propagation logic—there's no logic that blocks updates if label color fields 
are missing, but the cache can get stuck and prevent updates from showing up in 
charts. This was improved in later versions of Superset, so upgrading will 
resolve the issue for good. More technical details are available in the code 
and related issues: [issue 
32784](https://github.com/apache/superset/issues/32784), [color scheme caching 
logic](https://github.com/apache/superset/blob/93583220a7aa4debeaf3fd4a6cade9f771ee8c2f/superset-frontend/src/dashboard/util/charts/getFormDataWithExtraFilters.ts).
   
   
   <!-- 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/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/54f214d9-19ac-4f94-81bf-7b0cebd6fa3e?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[!
 [Share on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33839)


-- 
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]

Reply via email to