Workflow tool: empty subagent result set iterated as success ('{} is not iterable' at workflow.js:135) produces false clean report
Open 💬 0 comments Opened Jul 7, 2026 by marshallcourchaine-debug
A Workflow-tool run whose subagents returned an empty/malformed result set crashed with Error: {} is not iterable at workflow.js:135:46 — and in a related failure mode, an empty input set flowed through a verifier stage and produced a false "clean bill of health" (zero findings reported as success). ~926K subagent tokens were spent producing nothing usable.
Expected:
- An empty or schema-invalid subagent result set should be treated as a stage failure (retry/surface), never silently iterated or passed downstream as "no findings".
- The engine should validate stage inputs are non-empty before fan-out stages consume them, or at minimum surface a warning in the run result.
Environment: Claude Code CLI on Windows 11, PowerShell harness. Observed 2026-06/2026-07 across two separate sessions.