Distinguish loading, empty and failed workflow and policy lists #384

Closed
opened 2026-10-27 13:36:07 +00:00 by sam · 0 comments
Owner

The existing issue covers failed workflow-run fetches appearing empty. The recording additionally shows No workflows and No policies yet flashing during initial loading. Reproduce these paths and make loading, successful empty responses and failures distinct in workflow lists, run lists and organisation policies.

Acceptance criteria

Slow initial responses never show a false empty state. Failed fetches show an error and a working retry. Truly empty successful responses retain the appropriate empty state.

Notes

Loading, successful empty results and failures are now distinct for workflows, workflow runs and policies. Recent-run and run-list errors retain visible retries; stale workflow responses cannot overwrite the active selection. Browser checks cover delayed policies/definitions, unreadable run responses and successful retry.

Close reason

Implemented and verified in 57456b3e. Full quality gate passed, seven targeted local browser checks passed, and real audit-name save/readback was verified with the original setting restored. Per-issue acceptance evidence is recorded in notes.


Imported from beads archie-core-okjiv · GitHub #1632 · type bug · priority P3 · created 2026-10-11 · closed 2026-10-16

The existing issue covers failed workflow-run fetches appearing empty. The recording additionally shows No workflows and No policies yet flashing during initial loading. Reproduce these paths and make loading, successful empty responses and failures distinct in workflow lists, run lists and organisation policies. ### Acceptance criteria Slow initial responses never show a false empty state. Failed fetches show an error and a working retry. Truly empty successful responses retain the appropriate empty state. ### Notes Loading, successful empty results and failures are now distinct for workflows, workflow runs and policies. Recent-run and run-list errors retain visible retries; stale workflow responses cannot overwrite the active selection. Browser checks cover delayed policies/definitions, unreadable run responses and successful retry. ### Close reason Implemented and verified in 57456b3e. Full quality gate passed, seven targeted local browser checks passed, and real audit-name save/readback was verified with the original setting restored. Per-issue acceptance evidence is recorded in notes. --- _Imported from beads `archie-core-okjiv` · GitHub #1632 · type bug · priority P3 · created 2026-10-11 · closed 2026-10-16_
sam added the lowbug labels 2026-10-27 13:36:07 +00:00
sam self-assigned this 2026-10-27 13:36:07 +00:00
sam closed this issue 2026-10-27 13:36:07 +00:00
sam added a new dependency 2026-11-14 14:45:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#384