Relationships
#4892 Workflow pre-validation refuses a method argument supplied as a global argument when the definition authors a methods.<method>.arguments block
Opened by zack · 11/18/2026· Shipped 11/19/2026
Summary
Workflow pre-validation refuses a definition whose method argument is supplied as a global argument whenever the definition also has an authored methods.<method>.arguments block, even an empty one. The same step runs fine locally and when the block is omitted.
Reproduction
type: command/shell
name: g-run
globalArguments:
run: echo hi
methods:
execute:
arguments: {}Run execute from a workflow step. Validation fails with expected string, received undefined at "run". Change methods to {} and the step runs and prints hi.
Cause
ValidationService.validateMethodArguments (src/domain/models/validation_service.ts) parses the authored methods.<method>.arguments block on its own against the method's argument schema. It never merges in the definition's global arguments, the way execution does (unexpressioned globals under method arguments). A required method argument authored as a global therefore reads as missing. When no arguments block is authored the check is skipped, which is why methods: {} works.
Expected
Pre-validation parses the same merge execution parses: static global arguments the method schema declares, overlaid by the authored method arguments.
Notes
Found while triaging swamp-club#4891, where it forced that issue's reproduction to use methods: {} and hid the bug in a first round of testing. It predates swamp-club#4887 and is unrelated to that fix.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.