-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Labels
Description
Bug description:
Changing a service status from Ready → Active throws an error in the UI.
Despite the error, after refreshing the page the service status is actually changed to Active, indicating the backend operation succeeds but the frontend reports failure.
Expected behavior:
- Changing service status from Ready → Active should:
- Complete without UI errors when the backend succeeds
- Update the status immediately in the UI
- Errors should be shown only when the backend operation truly fails
- Loading/error states must be cleared correctly after the response
Logs:
Request URL
https://ruuter.test.buerokratt.ee/v2/private/services/services/status
Request Method: POST
Status Code: 500 Internal Server Error
Additional information:
- Repro: change service status Ready → Active
- UI shows error, but refresh reveals status is Active
- Strong indication of frontend/backend response handling mismatch
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Ready