Eve library

UX-006 Certification: Provider Failover Visibility Journey

Guide

Revision 1

On this page

Date: 2026-02-22
Checklist Item: UX-006
Ticket: ISIS-0231

Journey Scope#

User state: authenticated operator
Journey: detect degradation -> understand failover routing -> refresh -> confirm recovery
Coverage target: failover signals are visible and understandable during both degraded and recovered snapshots

Evidence Matrix#

Requirement Evidence Status
Degraded failover state is visible apps/isis/web/src/pages/ProvidersPage.spec.tsx test makes failover transitions visible and understandable during degradation and recovery asserts degraded snapshot rendering: Primary provider: runcomfy, Failover count: 8, Provider health: Unhealthy, queue Status: Unhealthy, and provider error runpod transport timeout. Pass
Failover cause/context is understandable Same test verifies queue health error context (runpod adapter degraded; routing to fallback provider) is rendered in the operational view. Pass
Recovery path is visible after operator refresh Same test clicks Refresh snapshot, asserts second snapshot fetch, and verifies recovered state (Primary provider: runpod, Provider health: Healthy, queue Status: Healthy). Pass
Operator journey requirement Test executes authenticated provider operations surface with realistic degraded->recovered telemetry transitions, validating comprehensible operator workflow end-to-end. Pass

Reproduction Commands#

bash
pnpm --filter @isis/web exec vitest run src/pages/ProvidersPage.spec.tsx