When an operator action fails, the dashboard surfaces nothing. Pressing Stop on a running task issued POST /api/tasks/3/action, received 403, and the only evidence anywhere was a browser console line: "Failed to load resource: the server responded with a status of 403". The page itself showed no error, no toast, no change of state -- the button simply appeared to do nothing.
This is how archie-core-440c (every dashboard mutation 403s behind a TLS-terminating reverse proxy) went unnoticed: the operator pressed Stop, saw nothing happen, and reasonably concluded the task was unstoppable rather than that the request had been refused. The bug was only found by opening devtools.
Confirmed live 2026-08-25 while signed in to the production dashboard.
Why this is its own bead
440c fixes the 403. This bead fixes the fact that ANY failed action is invisible -- a 500, a store failure, a refused state transition, an expired session -- and each of those has its own way of going wrong. Fixing only 440c leaves the next failure equally silent.
Note internal/webui/api_tasks.go already returns distinguishable, human-readable failures ("missing CSRF header", "cross-origin mutation refused", "runtime task control is unavailable"). The server side is doing its job; the client discards it.
What is needed
A failed action tells the operator it failed, in the UI, with the server's reason where one is given.
The distinction that matters most: refused (403, bad state, not permitted) versus broken (5xx, network). The operator's next move differs -- the first is "you cannot do that", the second is "try again or check the daemon".
A 401 or an expired forward-auth session should prompt re-authentication rather than reading as a generic failure, since the deployment sits behind Authelia.
The optimistic UI must not show an action as applied when it was refused.
Per CLAUDE.md the frontend is one folder per feature under ui/src/ with shared primitives in ui/src/base -- error surfacing used by more than one feature belongs in base, extracted on the SECOND real consumer, not in anticipation. Remember ui/dist is committed: run task ui and commit the rebuilt output in the same change.
Steps to Reproduce
Load the dashboard in a deployment where mutations fail (any 440c-affected proxied deployment reproduces it directly).
Press Stop, Retry, Abandon or Archive on a task.
Observe the request fails in devtools while the page reports nothing.
Acceptance Criteria
A failed operator action is reported in the dashboard with the server's reason where supplied; refused and broken failures are distinguishable to the operator; an authentication failure prompts re-auth rather than a generic error; no optimistic state change survives a failed request; dashboard tests cover a refused action, a server error and a network failure; ui/dist is rebuilt and committed.
Close reason
Closed
Imported from beads archie-core-h3lg · GitHub #629 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-06
When an operator action fails, the dashboard surfaces nothing. Pressing Stop on a running task issued POST /api/tasks/3/action, received 403, and the only evidence anywhere was a browser console line: "Failed to load resource: the server responded with a status of 403". The page itself showed no error, no toast, no change of state -- the button simply appeared to do nothing.
This is how archie-core-440c (every dashboard mutation 403s behind a TLS-terminating reverse proxy) went unnoticed: the operator pressed Stop, saw nothing happen, and reasonably concluded the task was unstoppable rather than that the request had been refused. The bug was only found by opening devtools.
Confirmed live 2026-08-25 while signed in to the production dashboard.
## Why this is its own bead
440c fixes the 403. This bead fixes the fact that ANY failed action is invisible -- a 500, a store failure, a refused state transition, an expired session -- and each of those has its own way of going wrong. Fixing only 440c leaves the next failure equally silent.
Note internal/webui/api_tasks.go already returns distinguishable, human-readable failures ("missing CSRF header", "cross-origin mutation refused", "runtime task control is unavailable"). The server side is doing its job; the client discards it.
## What is needed
- A failed action tells the operator it failed, in the UI, with the server's reason where one is given.
- The distinction that matters most: refused (403, bad state, not permitted) versus broken (5xx, network). The operator's next move differs -- the first is "you cannot do that", the second is "try again or check the daemon".
- A 401 or an expired forward-auth session should prompt re-authentication rather than reading as a generic failure, since the deployment sits behind Authelia.
- The optimistic UI must not show an action as applied when it was refused.
Per CLAUDE.md the frontend is one folder per feature under ui/src/<feature> with shared primitives in ui/src/base -- error surfacing used by more than one feature belongs in base, extracted on the SECOND real consumer, not in anticipation. Remember ui/dist is committed: run `task ui` and commit the rebuilt output in the same change.
## Steps to Reproduce
1. Load the dashboard in a deployment where mutations fail (any 440c-affected proxied deployment reproduces it directly).
2. Press Stop, Retry, Abandon or Archive on a task.
3. Observe the request fails in devtools while the page reports nothing.
## Acceptance Criteria
A failed operator action is reported in the dashboard with the server's reason where supplied; refused and broken failures are distinguishable to the operator; an authentication failure prompts re-auth rather than a generic error; no optimistic state change survives a failed request; dashboard tests cover a refused action, a server error and a network failure; ui/dist is rebuilt and committed.
### Close reason
Closed
---
_Imported from beads `archie-core-h3lg` · GitHub #629 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-06_
sam
added the mediumbug labels 2026-10-27 13:40:02 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When an operator action fails, the dashboard surfaces nothing. Pressing Stop on a running task issued POST /api/tasks/3/action, received 403, and the only evidence anywhere was a browser console line: "Failed to load resource: the server responded with a status of 403". The page itself showed no error, no toast, no change of state -- the button simply appeared to do nothing.
This is how archie-core-440c (every dashboard mutation 403s behind a TLS-terminating reverse proxy) went unnoticed: the operator pressed Stop, saw nothing happen, and reasonably concluded the task was unstoppable rather than that the request had been refused. The bug was only found by opening devtools.
Confirmed live 2026-08-25 while signed in to the production dashboard.
Why this is its own bead
440c fixes the 403. This bead fixes the fact that ANY failed action is invisible -- a 500, a store failure, a refused state transition, an expired session -- and each of those has its own way of going wrong. Fixing only 440c leaves the next failure equally silent.
Note internal/webui/api_tasks.go already returns distinguishable, human-readable failures ("missing CSRF header", "cross-origin mutation refused", "runtime task control is unavailable"). The server side is doing its job; the client discards it.
What is needed
Per CLAUDE.md the frontend is one folder per feature under ui/src/ with shared primitives in ui/src/base -- error surfacing used by more than one feature belongs in base, extracted on the SECOND real consumer, not in anticipation. Remember ui/dist is committed: run
task uiand commit the rebuilt output in the same change.Steps to Reproduce
Acceptance Criteria
A failed operator action is reported in the dashboard with the server's reason where supplied; refused and broken failures are distinguishable to the operator; an authentication failure prompts re-auth rather than a generic error; no optimistic state change survives a failed request; dashboard tests cover a refused action, a server error and a network failure; ui/dist is rebuilt and committed.
Close reason
Closed
Imported from beads
archie-core-h3lg· GitHub #629 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-06