You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(dashboard): failed refresh leaves the button loading forever #2682
When refreshing the current dashboard, a failed detail request leaves the refresh action pending forever. The refresh button remains in its loading state even though the request layer reports the error.
Steps to Reproduce
Open an existing dashboard.
Make the dashboard detail endpoint fail, for example by disconnecting the network or returning HTTP 500.
Click the dashboard refresh button.
Expected Behavior
The refresh attempt settles after the request fails and the refresh button stops spinning.
Actual Behavior
refreshCurrentDashboard wraps getDashboardById in a Promise with only a resolve path. A rejection never settles the outer Promise, so DashboardContent never clears refreshLoading.
Logs
The request layer surfaces the HTTP or network error, but the refresh Promise remains pending.
Screenshots or Additional Context
The failure path is deterministic in the dashboard store action on current main. The request helper rejects on both business and network failures.
Impact
Dashboard refresh appears permanently stuck after a transient backend or network error.
Workaround
Reload the page.
Submission Checklist
Reproduced on the selected Chat2DB edition.
Searched existing issues and pull requests for duplicates.
Thanks for the clear report. I understand that when getDashboardById rejects during refreshCurrentDashboard, the outer Promise remains pending and DashboardContent never clears refreshLoading.
Please add the missing required environment details: Operating System and Operating System Version. Since this occurs in both Web and Desktop deployments, note the OS/version used for each reproduced deployment if they differ. That is the smallest remaining detail needed for maintainers to evaluate the failure path and its regression coverage.
Activity
github-actions commentedon Aug 11, 2026
Thanks for the clear report. I understand that when
getDashboardByIdrejects duringrefreshCurrentDashboard, the outer Promise remains pending andDashboardContentnever clearsrefreshLoading.Please add the missing required environment details: Operating System and Operating System Version. Since this occurs in both Web and Desktop deployments, note the OS/version used for each reproduced deployment if they differ. That is the smallest remaining detail needed for maintainers to evaluate the failure path and its regression coverage.