asadjan4611 opened a new issue, #17984:
URL: https://github.com/apache/dolphinscheduler/issues/17984

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   In the workflow definition list page, if the list API request fails once 
(for example due to network error), the page stays in loading state and further 
table requests are blocked.
   
   After that failure, actions like search, page change, and refresh do not 
trigger new data fetches until the whole page is reloaded.
   
   ### What you expected to happen
   
   The loading state should always be cleared even when the API request fails, 
and the user should be able to retry immediately (search/page change/manual 
refresh) without reloading the page.
   
   
   ### How to reproduce
   
   1. Open **Project -> Workflow Definition List**.
   2. Open browser DevTools and switch network to **Offline** (or block the 
workflow list API request).
   3. Trigger table load (initial load, search, or pagination).
   4. Restore network to Online.
   5. Trigger search or page change again.
   
   Result: table still behaves as locked in loading flow and does not recover 
correctly without page reload.
   
   
   ### Anything else
   
   This seems to happen because loading state is set to true before request, 
but on rejection path it is not reset in a finally/catch flow.  
   A safe fix is to always reset loading state in `finally` and show an error 
message on failure.
   
   Suggested area:
   - `dolphinscheduler-ui/src/views/projects/workflow/definition/use-table.ts`
   - `getTableData(...)` / `loadingRef` handling
   
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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

Reply via email to