POST /api/v1/cancel/(workflow-run|method-run)/<id> returns {"status":"cancelled"} as soon as an AbortController is aborted. Aborting is not cancelling: for in-process runs the abort is purely cooperative, so a hung or stuck run keeps executing while the caller is told it stopped. There is no later correction — the response is the only signal the client ever gets.

swamp workflow cancel --run <id> --server then prints Cancelled run <id> on server for a run that is still going.

Why the abort does not stop a stuck run

RunCancelRegistry.cancel and ActiveRunRegistry.cancel only call controller.abort(...) (src/serve/run_cancel_registry.ts:63-72, src/serve/active_run_registry.ts:141-146).
The workflow engine only tests options.signal.aborted at step boundaries (src/domain/workflows/execution_service.ts:1918, 2317, 2361). A step that is already stuck never reaches one.
Extension methods execute in-process via InProcessExecutor — same process as swamp serve. The signal is handed to the method context (src/libswamp/models/run.ts:744) but there is no subprocess to kill and no race against the signal, so a method that ignores ctx.signal (infinite loop, blocking call, fetch without the signal) runs to completion.

Consequences beyond the wrong status: the run stays in the registry, and because the finally that calls flushLocks() never runs, it keeps holding its model locks. The existing backstops do not help — --max-run-duration fires the same cooperative abort (src/serve/active_run_registry.ts:100-108), and stale-run reaping only rewrites tracker records. Restarting serve is the only way out.

Contrast with the two paths that do work:

Local swamp workflow cancel / swamp model cancel use killProcessTree — SIGTERM, 2s poll, then SIGKILL to the process and its children (src/infrastructure/process/process_kill.ts:120-142).
Worker-dispatched steps send runner.cancel and then unconditionally child.kill() after RUNNER_CANCEL_GRACE_MS (src/worker/dispatch_handler.ts:258-274), which works because the runner is a separate process.

Steps to reproduce

Start swamp serve.
Run a workflow whose step calls a model method that ignores ctx.signal (e.g. a loop with a plain await new Promise(r => setTimeout(r, 1000))).
POST /api/v1/cancel/workflow-run/<runId> (or swamp workflow cancel --run <id> --server).

Actual: HTTP 200 {"status":"cancelled"}; the run keeps emitting events, stays in GET /api/v1/health activeRuns, and holds its locks. Expected: the response distinguishes "abort delivered" from "run stopped".

Suggested direction

Return a status that means what happened — e.g. cancellation_requested — and let the caller confirm termination (poll the active-run list, or have the endpoint wait a bounded grace period for the run to leave the registry before answering). A force path matching the worker's grace-then-kill behaviour would need out-of-process execution for in-process runs, so it is a larger change; at minimum the reported status should stop claiming a cancellation that did not happen.

Found while triaging #1536 (adding --server support to swamp model cancel), which would inherit this same misreporting.

02Bog Flow

Shipped

8/20/2026, 1:07:10 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/19/2026, 11:07:26 PM

stack72 commented 8/20/2026, 1:07:18 AM

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

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

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)

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

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

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

--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: update cancel endpoint response statuses in REST API reference and workflows page

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

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

serve: include workflowName in HealthSnapshotSchedule

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)

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

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

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

Docs: update workflow reference to include trigger in JSON output shapes

@swamp/git branch and push methods fail data naming when branch contains '/'

Docs: update workflow-placement.md for job/workflow-level placement inheritance

feat(serve): use identifiable OAuth client_name instead of random UUID

@swamp/git does not pass AbortSignal to Git subprocesses

Global Secret Manager methods build an invalid regional parent

Document model.method() support in assert expressions

No way to store code-review results — verdicts, findings, and cost are not persisted for any repo

Redaction regex boundary bug: label_base64 secrets with an unrecognized label pass through unredacted (e.g. swamp_ API keys)

User token page (/u/<user>) shows only "swamp_..." for every API key, making leaked-key identification impossible

upstream_state treats sparse-fetch branches as having no upstream

Add native support for the Pi coding harness

Cloud Build create supplies project instead of required projectId path parameter

workflows: support labels/target/platform at job and workflow level

swamp access grant create never registers the grant — a --deny created this way silently fails open

Support credentials in datastore config (vault-resolvable)

swamp serve OOMs on repos with 2000+ model definitions

Serve telemetry attribution for collectives

Extension workflows: no way to override trigger configuration

Add a list/discover method to the generated @swamp/aws types — no way to enumerate resources in a region

Document @vault= prefix for webhook secrets in serve.yaml

swamp access grant create installs an unrelated extension from the registry

docs: document SWAMP_API_KEY headless OAuth bootstrap for swamp serve

workflow-succeeded selects the globally-latest run, so siblings block each other under parallel use

swamp serve: webhook secrets should support @vault= resolution

Misleading collective_not_trusted auto-resolve error when a local source extension transiently fails to index during workflow validate

datastore setup: symlinks not counted in bytesCopied, causing misleading '(0B)' output

vault.get() CEL error embeds raw newline when wrapped by model resolver, producing broken output

Feature: user-configurable redaction rules (.swamp/redaction.yaml)

Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit

Sync every signup to Attio, and backfill the existing population (#809 follow-up)

@swamp/issue-lifecycle probes /api/health, which swamp-club stopped serving when the Fresh scaffold stubs were removed

Lab lifecycle POST rejects any payload string that starts with a dollar sign, not just operator keys

Feed: detect and gracefully handle dead (404) post links (link rot)

/feed: per-post unread indicators and mark-as-read to track reading progress

/feed: filter and search by author, title/text, and topic

Add a :micdrop: emoji / reaction shortcode (swamp-native art included)

Push down the two cheap leaderboard scans: ghost-gate dictionary and eventCounts owner filter