With the API down, the same outage renders three ways: red bordered boxes with the message twice (dashboard), a centred card (Tasks), and red text three times (Status). Elsewhere errors are bare red paragraphs: ui/src/settings/VersionsCard.vue:170, 212, ServicesCard.vue:111, CanaryStatusCard.vue:160, ui/src/org/OrgAccessPage.vue:108, ui/src/audit/DenialsPage.vue:38-41, ui/src/accounts/PersonalTokensCard.vue:85, ui/src/audit/AuditPage.vue:411-414, ui/src/settings/ExtensionsPage.vue:185 (styled as a hint).
Many error states have no Retry, so recovery needs a page reload: task panels and the task list (ui/src/tasks/TasksState.vue, PanelError.vue, TaskLogs.vue:226-231), Harness (ui/src/harness/HarnessPage.vue:112-115), bindings, mappings, members, workspaces, tokens.
Action errors in org and accounts pages show at the top of the page, far from the form that raised them; bindings and mappings show them beside the buttons.
Done when: read failures use the destructive Alert with Retry where the data would be, the page-level outage message is not repeated per section, and action errors sit beside their form.
With the API down, the same outage renders three ways: red bordered boxes with the message twice (dashboard), a centred card (Tasks), and red text three times (Status). Elsewhere errors are bare red paragraphs: `ui/src/settings/VersionsCard.vue:170, 212`, `ServicesCard.vue:111`, `CanaryStatusCard.vue:160`, `ui/src/org/OrgAccessPage.vue:108`, `ui/src/audit/DenialsPage.vue:38-41`, `ui/src/accounts/PersonalTokensCard.vue:85`, `ui/src/audit/AuditPage.vue:411-414`, `ui/src/settings/ExtensionsPage.vue:185` (styled as a hint).
Many error states have no Retry, so recovery needs a page reload: task panels and the task list (`ui/src/tasks/TasksState.vue`, `PanelError.vue`, `TaskLogs.vue:226-231`), Harness (`ui/src/harness/HarnessPage.vue:112-115`), bindings, mappings, members, workspaces, tokens.
Action errors in org and accounts pages show at the top of the page, far from the form that raised them; bindings and mappings show them beside the buttons.
Done when: read failures use the destructive Alert with Retry where the data would be, the page-level outage message is not repeated per section, and action errors sit beside their form.
Fixed in f37f6e24 and pushed. New components/ui ReadError (destructive Alert + message + optional Retry button) is the single read-error presentation, now used by Versions, Services, Canary, OrgAccess, Denials, Tokens, Audit, Extensions, Harness and Status (one page-level error via catalogError instead of one per card). PanelError is the same alert for task panels; TasksState's error kind, the attempts panel and the task-log pane all offer Retry (wired to load/refreshAll). Org policy save errors moved beside the Save button (saveError), load errors stay page-level with Retry. Verified: task check passed; e2e loading-errors + seeded pass against the seeded stack.
Fixed in f37f6e24 and pushed. New components/ui ReadError (destructive Alert + message + optional Retry button) is the single read-error presentation, now used by Versions, Services, Canary, OrgAccess, Denials, Tokens, Audit, Extensions, Harness and Status (one page-level error via catalogError instead of one per card). PanelError is the same alert for task panels; TasksState's error kind, the attempts panel and the task-log pane all offer Retry (wired to load/refreshAll). Org policy save errors moved beside the Save button (saveError), load errors stay page-level with Retry. Verified: task check passed; e2e loading-errors + seeded pass against the seeded stack.
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.
With the API down, the same outage renders three ways: red bordered boxes with the message twice (dashboard), a centred card (Tasks), and red text three times (Status). Elsewhere errors are bare red paragraphs:
ui/src/settings/VersionsCard.vue:170, 212,ServicesCard.vue:111,CanaryStatusCard.vue:160,ui/src/org/OrgAccessPage.vue:108,ui/src/audit/DenialsPage.vue:38-41,ui/src/accounts/PersonalTokensCard.vue:85,ui/src/audit/AuditPage.vue:411-414,ui/src/settings/ExtensionsPage.vue:185(styled as a hint).Many error states have no Retry, so recovery needs a page reload: task panels and the task list (
ui/src/tasks/TasksState.vue,PanelError.vue,TaskLogs.vue:226-231), Harness (ui/src/harness/HarnessPage.vue:112-115), bindings, mappings, members, workspaces, tokens.Action errors in org and accounts pages show at the top of the page, far from the form that raised them; bindings and mappings show them beside the buttons.
Done when: read failures use the destructive Alert with Retry where the data would be, the page-level outage message is not repeated per section, and action errors sit beside their form.
Fixed in
f37f6e24and pushed. New components/ui ReadError (destructive Alert + message + optional Retry button) is the single read-error presentation, now used by Versions, Services, Canary, OrgAccess, Denials, Tokens, Audit, Extensions, Harness and Status (one page-level error via catalogError instead of one per card). PanelError is the same alert for task panels; TasksState's error kind, the attempts panel and the task-log pane all offer Retry (wired to load/refreshAll). Org policy save errors moved beside the Save button (saveError), load errors stay page-level with Retry. Verified: task check passed; e2e loading-errors + seeded pass against the seeded stack.Fixed in
f37f6e24and pushed to main. Gate: task check exited 0 on the committed tree.