Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesstack72

Relationships

#1722 serve: include workflowName in HealthSnapshotSchedule

Opened by stack72 · 8/19/2026· Shipped 8/19/2026

Problem

The HealthSnapshotSchedule interface in src/serve/health_collector.ts only includes workflowId (the UUID), not the human-readable workflowName. This means the health endpoint (GET /health), the SSE health stream (GET /api/v1/health/stream), and any consumer of the health snapshot (including the new dashboard) can only display UUIDs for scheduled workflows instead of their names.

Proposed Change

Add workflowName: string to the HealthSnapshotSchedule interface and populate it in the HealthCollector.collect() method.

File: src/serve/health_collector.ts

The ScheduleProvider.listSchedules() returns entries with workflowId. The collector needs to resolve the workflow name, either by:

  1. Having the ScheduleProvider include the name in its schedule entries (the ScheduledExecutionService already knows the workflow definition when it registers the schedule)
  2. Or looking up the workflow name in the collector via the workflow repository

Option 1 is cleaner — the ScheduledExecutionService has access to the workflow definition at registration time and can store the name alongside the ID.

Current interface:

export interface HealthSnapshotSchedule {
  readonly workflowId: string;
  readonly cronExpression: string;
  readonly nextRun: string | null;
  readonly running: boolean;
}

Proposed interface:

export interface HealthSnapshotSchedule {
  readonly workflowId: string;
  readonly workflowName: string;
  readonly cronExpression: string;
  readonly nextRun: string | null;
  readonly running: boolean;
}

Also update the basic /health endpoint in src/cli/commands/serve.ts (line ~3623) which constructs the same schedule list without the name.

Context

The dashboard's Schedules view and Overview panel currently show UUIDs like 05345645-46c6-41b2-86d8-ed3fcdedef38 instead of the workflow name system-health. This is the same data the CLI's GET /health endpoint returns.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 4 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

8/19/2026, 10:46:53 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack728/19/2026, 5:17:02 PM

Sign in to post a ripple.