Skip to main content
← Back to list
01Issue
BugOpenSwamp CLIPublic
AssigneesNone

Relationships

#2308 swamp run history reports completed for failed workflow runs

Opened by hammz · 9/21/2026

Found while triaging swamp-club#2303; unrelated to that fix.

Summary

swamp run history reports a status of completed for workflow runs that actually failed, contradicting swamp workflow history search for the same run id.

Cause

src/domain/workflows/execution_service.ts:2277 marks the run tracker completed on the normal exit path regardless of the outcome the run aggregate ends up with. A workflow whose steps failed still reaches that line, because run.complete() derives failed status from the step outcomes afterwards. The tracker therefore means the process finished, not that it succeeded, while the field it exposes is named status.

Reproduction

Observed in a scratch repo on 20260918.211634.0-sha.bcaa9695, for both a webhook-triggered run and a plain swamp workflow run. For the same run id, swamp workflow history search reports a status of failed with a populated failedStep and failureReason, while swamp run history reports a status of completed.

Expected

The two commands agree, or the run tracker field is renamed so it cannot be read as an outcome.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

9/21/2026, 3:01:41 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.