[P3] Runtime: explain suspended routes & provide context #113

New Issue

claude · 2026-04-01T22:55:25+02:00

claude commented

2026-04-01 22:55:25 +02:00

Parent Epic

Problem

The Runtime page shows 25/62 active routes, 37 suspended — but doesn't explain why most routes are suspended. A new user would be alarmed. Are they intentionally stopped? Failing? Not configured for recording?

Current State (screenshot: `ux-audit/06-runtime-overview.png`)

KPI strip shows ACTIVE ROUTES: 25/62 with 37 suspended in smaller text
No explanation of why routes are suspended
No link to the configuration that controls this
Route recording toggles exist in App Config detail but aren't cross-referenced here

Proposed Solution

1. Contextual Explanation

Add a tooltip or info callout:

ACTIVE ROUTES
25/62
37 suspended (not configured for recording)
ℹ Configure route recording in App Config

2. Route Status Breakdown

On the Runtime instance detail page, show route status with actionable context:

ROUTES (24 total)
  ● 10 recording    — actively sending execution data
  ○ 14 suspended    — not configured for recording
  
  [Configure Recording →]  (links to App Config detail)

3. Link Between Runtime and App Config

Route badges in Runtime instance view should indicate recording status
Clicking a suspended route should offer to enable recording
App Config detail already has route recording toggles — just needs cross-linking

Acceptance Criteria

Suspended route count includes explanatory context
Link to App Config route recording from Runtime page
Route recording status visible per-route in instance detail
Tooltip or callout explains the difference between active/suspended

## Parent Epic #100 ## Problem The Runtime page shows `25/62 active routes, 37 suspended` — but doesn't explain why most routes are suspended. A new user would be alarmed. Are they intentionally stopped? Failing? Not configured for recording? ## Current State (screenshot: `ux-audit/06-runtime-overview.png`) - KPI strip shows `ACTIVE ROUTES: 25/62` with `37 suspended` in smaller text - No explanation of why routes are suspended - No link to the configuration that controls this - Route recording toggles exist in App Config detail but aren't cross-referenced here ## Proposed Solution ### 1. Contextual Explanation Add a tooltip or info callout: ``` ACTIVE ROUTES 25/62 37 suspended (not configured for recording) ℹ Configure route recording in App Config ``` ### 2. Route Status Breakdown On the Runtime instance detail page, show route status with actionable context: ``` ROUTES (24 total) ● 10 recording — actively sending execution data ○ 14 suspended — not configured for recording [Configure Recording →] (links to App Config detail) ``` ### 3. Link Between Runtime and App Config - Route badges in Runtime instance view should indicate recording status - Clicking a suspended route should offer to enable recording - App Config detail already has route recording toggles — just needs cross-linking ## Acceptance Criteria - [ ] Suspended route count includes explanatory context - [ ] Link to App Config route recording from Runtime page - [ ] Route recording status visible per-route in instance detail - [ ] Tooltip or callout explains the difference between active/suspended

claude added the ui ux labels 2026-04-01 22:55:25 +02:00

claude referenced this issue

2026-04-01 22:56:35 +02:00

Epic: UX Audit — PMF Readiness for First Market Offer #100

claude commented

2026-04-01 23:11:41 +02:00

Design Specification

Change terminology: "suspended" → "not recording" (accurate description)
Change StatCard accent: warning → auto (not a warning state)
Add info tooltip: "Active routes counts routes configured for recording. Routes not recording still process messages normally."
Add "Configure" link → /admin/appconfig?app={appId}
Instance detail: route badges with green/grey dot indicating recording status (from routeRecording config)
Dismissible info callout on first view explaining the distinction

## Design Specification - Change terminology: "suspended" → "not recording" (accurate description) - Change StatCard accent: `warning` → `auto` (not a warning state) - Add info tooltip: "Active routes counts routes configured for recording. Routes not recording still process messages normally." - Add "Configure" link → `/admin/appconfig?app={appId}` - Instance detail: route badges with green/grey dot indicating recording status (from `routeRecording` config) - Dismissible info callout on first view explaining the distinction

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#113

[P3] Runtime: explain suspended routes & provide context #113