apache/superset

When loading a dashboard, an error associated with a previously deleted dashboard pops up.

Open

#32533 opened on Mar 6, 2025

View on GitHub
 (9 comments) (2 reactions) (1 assignee)TypeScript (72,837 stars) (17,291 forks)batch import
cares:presetdashboard:errorgood first issuehome:favorite

Description

Bug description

To reproduce the error - it is necessary 1)Create a dashboard - save it 2)Delete the newly created dashboard 3) go to any other dashboard and get the error 'There was an issue fetching the favorite status of this dashboard'.

I also noticed that if the dashboard is not deleted, then every time you go to the dashboard, requests will be executed. api/v1/dashboard/favorite_status/ and superset/log/?explode=event of the previous dashboard.

Screenshots/recordings

Created Dashboard with id = 258 Image

When loading a dashboard with id = 55 - you can see that some methods work with the old dashboard id 258. Image

Superset version

4.1.1

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Contributor guide

Tech stack
typescriptpythonreactflask
Domain
frontendbackendanalytics
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React state managementSuperset dashboard APIPython Flask backendBasic debugging skills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the frontend component responsible for fetching dashboard favorite status (likely in /superset frontend/src/dashboard/). The bug suggests that when a dashboard is deleted, the previous dashboard's ID is still cached or used in subsequent API calls. Check the useEffect cleanup or state management that stores the active dashboard ID. Also examine the backend endpoint /api/v1/dashboard/favorite status/ to see if it should handle deleted dashboards gracefully. The issue has an assignee, so check their linked PRs or comments for progress.