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

Relationships

#2602 Reports from failed workflow steps are persisted but not recorded on the run

Opened by stack72 · 9/28/2026· Shipped 9/28/2026

Problem

When a workflow step's model method fails, its method-scope reports (including the built-in @swamp/method-summary) are generated and persisted, but the resulting data artifacts are never recorded on the workflow run. The step shows no report artifacts, so run history, swamp data list --workflow --run and the dashboard's RunDetail cannot point at the report for exactly the step you most need to investigate.

Cause

MethodReportRunner.runFailed (src/domain/workflows/method_report_runner.ts:231) builds callbacks whose onReportCompleted ignores the reportDataHandles argument, and whose onReportFailed discards _dataHandles. runSucceeded (lines 107-160) collects both into the returned DataArtifactRef[], which the caller attaches to the step's dataArtifacts.

Expected

A failed step's persisted report artifacts are returned from runFailed and recorded on the step exactly as for a successful step. Add a test asserting that a failed step's run record includes the report-swamp-method-summary artifacts.

Context

Found while planning swamp-club#2595 (dashboard deep links to reports). For incident investigation, failed-step reports are the most important ones to link to.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 11 MOREREVIEW+ 16 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/28/2026, 11:23:15 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/28/2026, 10:40:38 PM

Sign in to post a ripple.