GitHub user dosubot[bot] added a comment to the discussion: Transaction heatmap unable to show in one of many accounts
<!-- Greeting --> Hi @siyu1212! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> This kind of user-specific "Unexpected Error" in Superset is often caused by differences in permissions, group memberships, or row-level security (RLS) filters. Even if the user has developer or admin rights, it's possible that their access to the underlying dataset(s) for the heatmap is restricted, or that an RLS filter is applied to their account or group, blocking data access and causing the chart to fail to load ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/security/manager.py)). Here are some steps to help diagnose and resolve the issue: - Compare the affected user's roles, group memberships, and dataset permissions with a user who can see the heatmap. Make sure the problematic user has access to the same datasets and dashboards. - Check if any RLS filters are applied to the dataset powering the heatmap. If so, verify whether the affected user is subject to stricter filters or exclusions. - Review the Superset backend logs right after reproducing the error with the affected user. The logs usually contain a more detailed error message or stack trace, which can pinpoint permission or RLS issues ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/base.py)). - Clear the user's session and browser cache, then have them log out and back in. If the user was deleted and re-added, lingering session or database references can sometimes cause persistent errors ([discussion](https://github.com/apache/superset/discussions/32808)). - If the problem persists, try the affected account on a different browser or device to rule out client-side issues. If you find a specific permission or RLS rule causing the problem, updating the user's roles, group memberships, or dataset access should resolve it. Let me know if you find anything specific in the logs or permission settings! <!-- 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/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d3a905c3-4c3f-4dc4-a925-f156dd995fa6?feedback_type=other)</sup> [](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/discussions/34249) GitHub link: https://github.com/apache/superset/discussions/34249#discussioncomment-13832531 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
