[Workflows] Parallel step reference - #7691
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Elastic Docs Style Checker (Vale)Summary: 3 suggestions found 💡 Suggestions (3): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
shahargl
left a comment
shahargl
left a comment
There was a problem hiding this comment.
Thanks Natasha — this is a strong, accurate parallel-step reference. I checked the technical claims against the engine/schema and they largely match.
Two small fixes requested below before merge. Everything else looks good (defaults, foreach context, branch limits, fail-fast vs settled, output shape, applies_to consistency).
| serverless: preview | ||
| ``` | ||
|
|
||
| Run branches at the same time and continue when all of them reach a terminal state. Choose one of two modes: dynamic fan-out (`foreach` plus `steps`) runs the same body once per item in a runtime list, and static branches (`branches`) run a fixed set of named branches that each do different work. A step can't use both. |
There was a problem hiding this comment.
Nit / Vale: "all of them" → prefer "every branch" (matches the wording already used in parallel.md).
Suggested:
Run branches at the same time and continue when every branch reaches a terminal state.| | Field | Description | | ||
| |---|---| | ||
| | `results[].index` | Zero-based branch position. Always present. | | ||
| | `results[].key` | For static branches, the branch `name`. For dynamic fan-out, the item captured when the step started. | |
There was a problem hiding this comment.
Clarify dynamic results[].key: in the engine this is the full captured item value (key: item), which can be an object (e.g. a whole ES hit), not just a short string/id.
Suggested:
| `results[].key` | For static branches, the branch `name`. For dynamic fan-out, the full item value captured when the step started (may be an object, not just a string). |
3 participants
Adds a reference page for the
parallelstep, which runs branches concurrently, and links to it from the flow control overview, the step type index, the cheat sheet, "Choose the right step", and the steps hub.Resolves #7248
Made with Cursor