When a workflow has more than one suspended manual_approval run whose prompts resolve differently from inputs, swamp workflow approvals --json displays the most recently evaluated prompt for every pending run. Each run retains its own persisted inputs, but the older run's displayed prompt is rewritten with the newer run's values.

This makes the displayed approval prompt fail to identify the exact suspended run being approved.

Environment

Swamp 20260818.015459.0-sha.7d509529
Local filesystem workspace on Linux

Reproduction

Create a workflow with required string input label and a manual approval prompt Approval marker: ${{ inputs.label }}.
Run it with label=marker-one; it suspends at approval.
Run it again with label=marker-two; it also suspends at approval.
Run swamp workflow approvals --json.

Actual result

The older run reports persisted input label: marker-one, but its listed prompt is Approval marker: marker-two. The newer run correctly displays Approval marker: marker-two.

Concrete run IDs from the reproduction:

workflow ID: 0c4c3de8-6f75-49d0-85b1-edda894d25c4
marker-one run: 9f3127a8-3d42-4077-a221-e5c1e4725afa
marker-two run: d4640821-6648-469a-9c5c-07ce0d114cc9

The suspended-run YAML files correctly retain their distinct inputs.

Expected result

Each pending approval must display the resolved prompt that belonged to that specific suspended run:

marker-one run: Approval marker: marker-one
marker-two run: Approval marker: marker-two

simultaneously. A manual approval is not meaningful when its prompt can describe a different suspended run.

Source diagnosis

Version-matched source was fetched with swamp source fetch.

src/cli/commands/workflow_approvals.ts provides YamlEvaluatedWorkflowRepository.findById(workflowId) to the approval service.
src/libswamp/workflows/approvals.ts declares evaluatedWorkflow outside the loop over suspended runs, resolves it once by workflow ID, and uses that prompt for every pending run of the workflow.
src/infrastructure/persistence/yaml_evaluated_workflow_repository.ts writes one evaluated artifact per workflow at .swamp/workflows-evaluated/workflow-{name}.yaml, not one per run.

The later evaluation therefore replaces the artifact that the earlier run's listing consults. Existing tests cover a single evaluated prompt, but not two suspended runs with distinct expression-resolved prompts.

Suggested repair and regression test

Persist the resolved manual-approval prompt, or an immutable evaluated-task snapshot, with the run/step when it enters waiting_approval; render the listing from that run-bound value. Do not re-evaluate the current workflow at listing time, because the definition or referenced values may change after suspension.

Add a regression test that creates the two suspended runs above and asserts that workflow approvals --json shows each run's own resolved prompt at the same time.

02Bog Flow

Shipped

8/18/2026, 4:21:08 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/18/2026, 2:57:00 PM

stack72 commented 8/18/2026, 4:25:49 PM

Thanks @jeremy for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

--ca-cert / SWAMP_CA_CERT are ignored when serve runs --auth-mode token — only DENO_CERT reaches the connection's TLS config (found validating #1748)

Only documented non-interactive auth puts the password in argv; the safe SWAMP_API_KEY path is undocumented

Retyping a model instance strands catalog rows no command can reclaim — prune matches on model_id, delete resolves the current type (follow-up to #1009)

Docs: update cancel endpoint response statuses in REST API reference and workflows page

docs: update vault audit trail reference for write operation support

docs: document --dashboard flag for swamp serve

ExtensionWorkflowRepository scans manifest.yaml as a workflow, emitting 'Unknown key manifestVersion' warning

Relative path for custom agent skills setup doesn't provision skills

swamp serve daemon enable: add --dashboard flag

CLI writes runtime state (lastStalenessWarning) into tracked .swamp.yaml, dirtying a committed config file

extension install serializes files[] in readdir order, producing machine-dependent reorder diffs in upstream_extensions.json

Workflow YAML rewritten in place: block-scalar description truncated, file left unparseable, and validate still reports PASSED

workflow validate does not resolve modelType on factory-pattern steps — a non-existent extension validates clean

vault.get() arguments are verbatim, so a per-target secret cannot be expressed in workflow YAML

Cancellation/--timeout skips remaining steps including `completed`/`always` branches; --timeout waits for the in-flight subprocess

Remote "write-bearing" classification is inferred from data-plane writes, not declared; external side effects can be re-executed on worker disconnect (docs say the opposite)

Audit timeline is not populated by swamp CLI commands unless the AI-tool hook fires (manual says recording is automatic)

manual_approval suspends the run while parallel sibling jobs are mid-flight; in-flight steps are torn down and left `running`

`workflow resume --from` does nothing for forEach steps whose template name contains `${{ }}`

Step-level dependsOn on a forEach step never evaluates true (except `always`)

rum/site-info: lookup GETs a non-existent endpoint, always 405

vault read-secret appends a newline to piped output

wss:// direct to serve's own TLS listener still fails on 20260817 — client ALPN lands on h2, WS-over-h2 unimplemented (follow-up to #1363)

serve: vault audit repository not wired up — audit trail always empty

Support Jira webhooks with X-Hub-Signature HMAC-SHA256 verification

Add typed read-only remote ref lookup to @swamp/git

pullChanged skips same-size updated files — size-only change detection ignores the index sha256

A run's terminal status reaches the shared datastore only when a later run happens to push it

workflow cancel --all on the serve host shuts down the serve process

Readability of tables in documentation

repo init/upgrade --tool kiro references .kiro/skills/ but installs skills to ~/.kiro/skills/

vault: audit trail should record put, delete, and annotate operations

data.findBySpec() returns only the first in-run record, not all of them, so an .all() assert silently checks one element

repo upgrade --tool kiro reports wrong changedFiles paths

Suppress boot-time "pulled extension(s) have missing source files" WRN when invoked command is `swamp extension install`

s3-datastore: a stale machine's sync pushes its old 'latest' pointer over the newer remote one, and the rollback is permanent

`search` → `list` aliases are hand-rolled Command clones, not aliases: 10 of 11 have drifted from their parent's option set

Make official Docker image OCI-compliant

Method-name collision between a base model type and an extending extension silently drops the whole extension file — no error, doctor reports pass

data prune still misclassifies live records as orphans on 20260820 (after #1396) — serve-minted token/grant records, and report data of every live workflow

vault put prompts for the secret before validating the vault name exists

workflow validate: false 'Missing required inputs' for CEL-templated globalArgs (${{ inputs.* }})

Add SWAMP_CLI_OUTPUT env var to control default output mode (plaintext/tui/json)

@swamp/git fetch: support local path as remote

Dispatched steps over 15 minutes cannot write results: dispatch credentials expire and never refresh

Concurrent pushes to one namespace fail with HTTP 409 ConditionalRequestConflict — the conditional PUT is never retried

serve: triggerSource not persisted to workflow run summary

dataOutputOverrides not applied during remote execution — ephemeral resources GC'd before override takes effect

extension rm also deletes the lockfile entry, and install on an empty lockfile is a silent success — rm/install is not a round trip

--max-run-duration only applies to detached runs, not attached runs

Cancel endpoint reports status: cancelled for runs it did not actually cancel

@swamp/git: no way to amend a commit, but push can --force

Installation with new account creation times out

pre-flight checks run on orchestrator, not on worker — breaks remote execution with filesystem-dependent checks

docs: document --remote-only flag for swamp serve

Swamp serve daemon doesn't run with --hot-reload

serve: include workflowName in HealthSnapshotSchedule

knowledge-base retrieve persists query output into the state resource, with lifetime infinite and the query text in the instance name

Skip 50MB monolithic index rewrite on v2 shard-first path

Share single AwsS3Client instance across lock, sync, and verifier

Double shard assembly per command lifecycle (pull + push both read all shards)

pullChanged never records commitSeq for shard-first (v2) index

localHasAllRemoteEntries() permanently blocks sidecar update on partial caches

serve: workflow.history.get cannot find CLI-created runs or look up by run ID

"TRIAL ENDED" modal shown to team plan user when toggling extension visibility

Concurrent suspended workflow runs can't be disambiguated from 'approvals'; fresh runs should supersede matching-input suspended runs

I _think_ I might like a guard in the trigger yaml

swamp cmds don't realise the user is sshed into the system

serve dashboard: add cluster.instances and serve.config endpoints

CEL expressions have timestamp/duration but no current-time value, so no guard can express "older than N"

Support direct type execution (@type) with --server

access token mint writes to user vault, not serve's _token-secrets control plane in HA mode

Generic OTLP endpoint appends signal path after query or fragment

Issue lifecycle start drops top-level issue comments

serve dashboard: add instanceId, triggerSource, and step progress to WorkflowRunSummary

Document worker affinity (affinity: true) for workflows and jobs

Datastore MongoDB driver leaks connections — 5960 accumulated over 8 days

workflow approvals displays the latest run's prompt for every suspended run

@swamp/git: add a read-only working-tree diff for pre-commit review

docs: document --oauth-client-name flag for swamp serve