Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

Relationships

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

Opened by svendowideit · 8/1/2026· Shipped 8/1/2026

Problem Statement

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
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

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
Editable. Press Enter to edit.

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.

Sign in to post a ripple.