In my other work, i'm often debugging systems where it's impossible to determine if a workflow / code step does not exist, was commented out, or was skipped due to some logic.

Proposed Solution

In swamp, it would be nice to have a record that a workflow step was skipped for a reason what that reason was, and what evaluation (including values) was used to trigger that (or not)

heck - being able to see why a step wasn't skipped would also give reasurance (or even iso9001 style assurance) that the defined process was correctly determined and adheared to.

Alternatives Considered

yeah, my agent told me to put it in the code :(

Additional Context

02Bog Flow

Shipped

8/1/2026, 11:15:21 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/1/2026, 10:11:51 PM

stack72 commented 8/1/2026, 11:15:28 PM

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

workflow placement: run a workflow transparently on a specified host, local or via swamp workers (incl. nested child workflows)

deprecated extensions are more prominent than I expected :)

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

Trigger schedule overrides require a swamp serve restart to take effect

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

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

swamp issue bug isn't auto-filling swamp version, OS and shell

Upgrade/Update causes odd locking issue on swamp deno

stale lock file not being cleaned up?

swamp auth login process fails when run remotely

can the combat log also tell me which hostname the command was run on?

add links to the docs for all account progress teasers

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

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

I _think_ I might like a guard in the trigger yaml

swamp command doesn't check cwd

Output a log line for steps skipped due to guards

Add a --release-notes option to `swamp update` (or even make it the default)

Running "swamp workflow run ..." in a subdir of the swamp repo fails

Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

Could not start dynamically linked executable: /home/sven/.swamp/bin/swamp

ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

Relationships

#1489 Output a log line for steps skipped due to guards

Problem Statement

Proposed Solution

Alternatives Considered

Additional Context

Shipped