Summary
Several dashboard pages expose a shell but do not explain whether the feature is empty, misconfigured, unreachable, or broken.
Areas
- Workflows
- Hands
- Channels
- Scheduler
- Approvals
- MCP
- Integrations
Expected
Each page should clearly distinguish empty, loading, error, and unreachable states, with a next-step action for the user.
Scope
- Audit and normalize page-level state handling.
- Introduce a shared status-banner or empty-state pattern.
- Add setup or smoke-test actions where possible.
Acceptance criteria
- Audited pages render distinct empty, error, and unreachable states.
- Each empty state includes at least one next action.
- Browser smoke tests cover the highest-traffic pages.
Source
Tracked from docs/implementation-backlog-2026-03-03.md.