Problem
When adding to a queue, the CLI requires --step=<flow_step_id> even when the flow has only one queueable step.
Current:
wp datamachine flows queue add 29 --step=12_e5eda239-5bd7-4ae6-89f1-e21909115c98_29 "My prompt"
The flow_step_id is awkward to look up every time.
Proposed Solution
If the flow has exactly one step with queue_enabled: true, auto-resolve the step:
wp datamachine flows queue add 29 "My prompt"
Only require --step when ambiguous (multiple queueable steps).
Benefit
Much friendlier for automation and CLI usage.
Problem
When adding to a queue, the CLI requires
--step=<flow_step_id>even when the flow has only one queueable step.Current:
wp datamachine flows queue add 29 --step=12_e5eda239-5bd7-4ae6-89f1-e21909115c98_29 "My prompt"The flow_step_id is awkward to look up every time.
Proposed Solution
If the flow has exactly one step with
queue_enabled: true, auto-resolve the step:wp datamachine flows queue add 29 "My prompt"Only require
--stepwhen ambiguous (multiple queueable steps).Benefit
Much friendlier for automation and CLI usage.