Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublicTeam
Assigneeszack

Relationships

#4828 workflow approve: add --resume to continue the run once all gates are decided

Opened by maxwalters · 11/17/2026· Shipped 11/17/2026

Problem

Continuing a workflow run that is paused on a manual_approval step takes two commands:

swamp workflow approve <workflow> <step> --run <id> --suspended-at <ts>
swamp workflow resume <workflow> --run <id>

The second command carries no new decision. approve already reports allGatesDecided: true, so the run is known to be ready to continue.

In scripts, the two-step form means holding the run id across both calls and checking two exit codes. For a person, a forgotten resume leaves a run approved but suspended, and nothing reports that state.

Proposed solution

Add a --resume flag to swamp workflow approve.

  • When the approval leaves every gate of the run decided, resume the run in the same invocation and report the resumed run's result.
  • When other gates are still pending, approve only, and say that the run was not resumed and which gates remain.
  • With --json, emit the approval document, then the same documents swamp workflow resume emits today.
  • The exit code is the resume's exit code when a resume ran.

The default stays as it is: without --resume, approve only records the decision.

Alternatives considered

  1. Make approve always resume once all gates are decided. Simpler, but it changes behaviour for anyone who approves ahead of time and resumes later.
  2. A new swamp workflow continue command that approves and resumes. It adds a command where a flag would do.
  3. Keep a local wrapper script. That is what we do now. Each repo has to write its own, and ours misread multi-document --json output twice before it was right.

Environment

swamp 20261113.232530.0-sha.492fb502, macOS, local repo, no serve.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 10 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/17/2026, 9:51:26 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
zack assigned zack11/17/2026, 8:04:47 PM
Editable. Press Enter to edit.

zack commented 11/17/2026, 9:51:27 PM

Thanks @maxwalters for reporting this! We shipped: Add an opt-in --resume flag to swamp workflow approve. When the approval leaves every gate decided (allGatesDecided), the same invocation resumes the run through the existing resume code path, extracted into shared functions in workflow_resume.ts and loaded by dynamic import only when a resume runs, and exits with the resume's exit code; otherwise it approves only and names the pending gates, now reported by libswamp approve as pendingGates. Under --server it never duplicates serve's auto-resume, says who continues the run, and surfaces serve's refusal when the approver lacks the run grant. Default behaviour without the flag is unchanged.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.