← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneeszack
Relationships
#4553 Skill workflow reference uses range() in a forEach example; swamp CEL has no range(), and workflow validate passes it anyway
Opened by zack · 11/9/2026· Shipped 11/9/2026
Description
The swamp skill's workflow reference shows a forEach over ${{ range(1, 97) }} (.claude/skills/swamp/references/workflow/reference.md, "forEach compatibility" example under guards). swamp's CEL environment has no range() function, so a workflow copied from that example:
- passes
swamp workflow validate(10/10 checks), but - fails at run time with:
Workflow execution failed: Invalid expression: found no matching overload for 'range(int, int)'
> 1 | range(1, 97)
^That's two problems:
- Docs: the bundled skill teaches agents a function that doesn't exist, so agents writing fan-out workflows hit this.
- Validation gap:
workflow validatedoesn't type-checkforEach.inexpressions, so an unknown function only shows up when the run starts.
Steps to reproduce
- Create a workflow with a step:
forEach: item: n in: ${{ range(1, 9) }} task: type: behavior behavior: <any> methodName: run
swamp workflow validate <name>: PASSEDswamp workflow run <name>: fails withfound no matching overload for 'range(int, int)'
Expected
- The skill example uses something that works (a list literal, an input, or data from
data.latest), or swamp provides arange()CEL function. swamp workflow validateparses and type-checksforEach.in(and other step expressions) against the CEL environment and reports unknown functions/overloads.
Environment
- Found on the branch for swamp-club#4534 (HEAD ecf6c21b4)
- Linux x86_64
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Sign in to post a ripple.