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

Relationships

#1468 workflow edit: after saving an invalid workflow, re-running edit reports "Workflow not found"

Opened by jasonbarnett · 7/29/2026· Shipped 7/30/2026

What happened

I created a workflow, opened it with swamp workflow edit, and fat-fingered a key (ependssss instead of dependsOn) before saving. When I ran swamp workflow edit info-pipeline again to fix it, it told me the workflow wasn't found:

$ swamp workflow edit info-pipeline
2026-07-29T22:27:21.609Z [WRN] workflow-repo: Skipping broken workflow
"info-pipeline": "Unknown key 'ependssss' on step 'example'. Did you mean
'dependsOn'? Valid step keys: name, description, task, forEach, dependsOn,
weight, concurrency, dataOutputOverrides, allowFailure, target, labels,
platform, queueTimeout, guard". Run 'swamp doctor workflows --json' to see all
errors. File: "/home/[REDACTED]/demo-ux-swamp/workflows/workflow-0459c615-a[REDACTED-PHONE]-654060a88941.yaml"

Error: Workflow not found: info-pipeline

In fairness, the warning does say what's wrong and points at swamp doctor workflows. But I use a lot of tools, and in the moment it read as a wall of text — I skimmed past it, saw Error: Workflow not found, and was confused, because I'd just been editing that workflow seconds earlier. The information I needed was there; the shape of the output meant I didn't take it in.

Steps to reproduce

swamp repo init
swamp workflow create info-pipeline
swamp workflow edit info-pipeline
# in $EDITOR: rename the step's 'dependsOn' key to 'ependssss', save, quit
swamp workflow edit info-pipeline    # "Workflow not found: info-pipeline"

Exit code 1. Passing the UUID instead of the name gives the same result, and the workflow also stops showing up in swamp workflow list, so I didn't have an obvious way back to it from the CLI. (swamp workflow validate info-pipeline and swamp doctor workflows both do find it and report the schema error correctly.)

What I expected

Mostly just to be able to re-run swamp workflow edit and get another crack at it. Since the mistake happened in the editor, going back to the editor is where my head was.

Ideally, closer to crontab -e: if what I save doesn't validate, it re-opens in my editor with my bad edits still there, so I can fix the typo instead of starting over or hunting down the file. I realize the exact interaction depends on $EDITOR and may not be straightforward, so I'm not attached to the mechanics — the parts that would have helped me are:

  • workflow edit opening the file even when it doesn't validate, rather than reporting it as not found
  • a chance to correct it in place, with the bad edits preserved
  • the validation error being the headline rather than a warning above it

Not urgent — nothing was lost, and swamp doctor workflows did point me at the file once I went looking. It just caught me off guard, so I figured it was worth mentioning.

Environment

  • swamp 20260729.212638.0-sha.45d9ed58
  • Linux 6.17.0-1019-aws, zsh, $EDITOR = Neovim
  • Fresh repo from swamp repo init, scaffold from swamp workflow create

#188 covered making workflow validate errors actionable for workflows that don't exist yet. This is a slightly different case: one that exists on disk but doesn't validate.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

7/30/2026, 12:03:31 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/29/2026, 10:49:17 PM
Editable. Press Enter to edit.

stack72 commented 7/30/2026, 12:03:40 AM

Thanks @jasonbarnett 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.