Aman-Mittal opened a new issue, #763:
URL: https://github.com/apache/fineract-backoffice-ui/issues/763

   ### Summary
   When `GET /savingsaccounts/{id}` fails (here a network failure), 
`/products/savings-accounts/view/{id}` shows only the breadcrumb ("Products › 
Savings Account Details") and an empty page. There's no error message, retry 
action, spinner or toast. The user can't tell whether the account is missing, 
loading or broken.
   
   ### Environment
   - App: https://aman-mittal.github.io/fineract-backoffice-ui (deployed 
`main`), `/products/savings-accounts/view/2`
   - Backend: `sandbox.mifos.community`, which briefly refused connections 
during the audit (`net::ERR_CONNECTION_CLOSED`). That outage is environmental. 
The UI's handling of it is the defect.
   - 2026-10-16
   
   ### Preconditions
   A savings account id, and any condition that makes the account request fail 
(offline, backend restart, 5xx).
   
   ### Steps to reproduce
   1. Open `/products/savings-accounts/view/{id}`.
   2. Make the account request fail (in DevTools, block `*/savingsaccounts/*` 
or go offline) and reload.
   
   ### Expected behavior
   The shared error state that other screens already use after #660 and #611 
("This … could not be loaded" with **Try again**), plus a toast for network 
errors.
   
   ### Actual behavior
   Console:
   ```
   net::ERR_CONNECTION_CLOSED  GET /businessdate
   net::ERR_CONNECTION_CLOSED  GET 
/savingsaccounts/2?staffInSelectedOfficeOnly=false&associations=all
   ```
   The DOM inside `main` is only the breadcrumb text. No `ion-spinner`, no 
`[role=alert]`, no toast. The state persisted (checked again about 3 s later).
   
   ### Evidence
   Live observation above. A screenshot was captured locally; uploading it to 
the issue was blocked in this session.
   
   ### Impact
   Staff looking up an account during an outage or backend hiccup see a blank 
page and may assume the account doesn't exist. Compare Interest Rate Charts, 
which shows "could not be loaded. TRY AGAIN".
   
   ### Suggested investigation
   The savings account view's load subscription probably has no `error` branch, 
or swallows it. Wire it to the shared load-error component, and check the loan, 
fixed and recurring deposit views for the same gap.
   
   ### Verification status
   Reproduced once (live outage). Not yet reproduced with deliberate request 
blocking.
   
   ### Related endpoints
   `GET /savingsaccounts/{id}?associations=all`
   
   ### Acceptance criteria
   - A failed account load shows an error state with a working Try again.
   - A unit test with an erroring service asserts the error state renders.
   
   ### Related issues
   #749 (similar silent-failure handling on config screens).


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