elastic · benironside · May 14, 2026
@@ -18,7 +18,7 @@ products:
 Composition lets one workflow call another. Done well, it turns a sprawling multi-purpose workflow into a small, testable parent that delegates to focused children. This page covers the authoring decisions: when to extract a child workflow, how to design its input and output contract, how to test it in isolation, and how to fan out to background jobs.
 
 :::{warning}
-Composition steps (`workflow.execute`, `workflow.executeAsync`, `workflow.output`, `workflow.fail`) are in technical preview in 9.4. Use them for prototypes and reusable utility workflows. Hold off on critical paths until composition reaches GA.
+Composition steps (`workflow.execute`, `workflow.executeAsync`, `workflow.output`, `workflow.fail`) are in technical preview. Use them for prototypes and reusable utility workflows. Hold off on critical paths until composition reaches GA.
 :::
 
 For the step parameter reference, refer to [Composition steps](/explore-analyze/workflows/steps/composition.md).

@@ -81,7 +81,7 @@ By default, if any step fails the entire workflow execution stops immediately (t
 
 You can configure `on-failure` at two levels:
 
-**Step-level** — applies to a specific step:
+**Step-level** — Applies to a specific step:
 
 ```yaml
 steps:
@@ -93,7 +93,7 @@ steps:
         delay: "5s"
 ```
 
-**Workflow-level** (configured under `settings`) — applies to all steps as the default error handling behavior:
+**Workflow-level** (configured under `settings`) — Applies to all steps as the default error handling behavior:
 
 ```yaml
 settings:

@@ -33,8 +33,8 @@

 **Cause.** One of three common causes:
 
 1. The workflow was disabled (`enabled: false`).
-2. The interval is shorter than 1 minute. 9.4 enforces a minimum of `1m` / `60s`. Pre-9.4 schedules with shorter intervals were auto-migrated on first edit.
+2. The interval is shorter than 1 minute. The minimum interval is `1m` / `60s`; schedules with sub-minute intervals from earlier versions were auto-migrated on first edit.
 3. A `drop` concurrency strategy is skipping new runs while a prior run is still executing.
 
 **Resolution.** Verify the workflow is enabled, check the interval in the YAML editor, and review execution history for `skipped` entries. For concurrency details, refer to [Settings concurrency control](/explore-analyze/workflows/authoring-techniques/pass-data-handle-errors.md).
@@ -343,9 +343,9 @@
 
 **Cause.** One of:
 
-- `settings.timeout` — the workflow's overall time budget was exceeded.
-- Concurrency with `cancel-in-progress` — a new execution kicked this one out.
-- Operator cancel — someone clicked **Cancel all** in the UI.
+- `settings.timeout` — The workflow's overall time budget was exceeded.
+- Concurrency with `cancel-in-progress` — A new execution kicked this one out.
+- Operator cancel — Someone clicked **Cancel all** in the UI.
 
 **Resolution.** The execution view shows the cancellation reason on the terminal state. Review it and adjust `settings.timeout` or the concurrency strategy if needed.
 
@@ -357,15 +357,15 @@
 
 **Cause.** Your user role is missing one of the Workflows feature privileges.
 
-**Resolution.** Ensure your role has at least `All` on the **Analytics > Workflows** feature. For finer-grained access, 9.4 introduces seven granular sub-feature privileges: `create`, `read`, `update`, `delete`, `execute`, `readExecution`, and `cancelExecution`. Refer to [Setup](/explore-analyze/workflows/get-started/setup.md).
+**Resolution.** Ensure your role has at least `All` on the **Analytics > Workflows** feature. For finer-grained access, seven granular sub-feature privileges are available: `create`, `read`, `update`, `delete`, `execute`, `readExecution`, and `cancelExecution`. Refer to [Setup](/explore-analyze/workflows/get-started/setup.md).
 
 ### Workflows isn't visible in {{kib}} [workflows-ts-ui-missing]
 
 **Symptom.** The **Workflows** navigation entry doesn't appear in {{kib}}.
 
 **Cause.** The `workflows:ui:enabled` advanced setting has been disabled, or the deployment doesn't have the required license or subscription tier.
 
-**Resolution.** In 9.4, `workflows:ui:enabled` defaults to `true`. If it has been explicitly disabled, re-enable it in **Advanced settings**. Confirm the deployment is on a supported tier (Enterprise license on Elastic Cloud Hosted or self-managed, or a Serverless project of the required type). Refer to [Setup](/explore-analyze/workflows/get-started/setup.md).
+**Resolution.** `workflows:ui:enabled` defaults to `true`. If it has been explicitly disabled, re-enable it in **Advanced settings**. Confirm the deployment is on a supported tier (Enterprise license on Elastic Cloud Hosted or self-managed, or a Serverless project of the required type). Refer to [Setup](/explore-analyze/workflows/get-started/setup.md).
 
 ## Still stuck [workflows-ts-still-stuck]
 

@@ -96,10 +96,10 @@ Every step type available for Elastic Workflows, ordered alphabetically. Use thi
 
 In addition to the steps listed previously, every configured {{kib}} connector exposes one or more `<connector>.<action>` step types. Common examples include:
 
-- `slack.postMessage` — post a message to a Slack channel.
-- `jira.createIssue` — create a Jira issue.
-- `pagerduty.triggerIncident` — page an on-call rotation.
-- `virustotal.scanFileHash` — scan a file hash.
+- `slack.postMessage` — Post a message to a Slack channel.
+- `jira.createIssue` — Create a Jira issue.
+- `pagerduty.triggerIncident` — Page an on-call rotation.
+- `virustotal.scanFileHash` — Scan a file hash.
 
 Because the available connector steps depend on which connectors your deployment has configured, they aren't enumerated here. Refer to the [{{kib}} connectors reference](kibana://reference/connectors-kibana.md) for the full catalog.
 

@@ -18,7 +18,7 @@
 Composition steps let one workflow invoke another. Use them to build reusable workflow building blocks, break long workflows into testable pieces, and fan out to background jobs.
 
 :::{warning}
-Composition steps (`workflow.execute`, `workflow.executeAsync`, `workflow.output`, `workflow.fail`) are in technical preview in 9.4. The parameter shapes can change in future releases. Use for prototypes and reusable utility workflows; hold off on critical paths until composition reaches GA.
+Composition steps (`workflow.execute`, `workflow.executeAsync`, `workflow.output`, `workflow.fail`) are in technical preview. The parameter shapes can change in future releases. Use for prototypes and reusable utility workflows; hold off on critical paths until composition reaches GA.
 :::
 
 ## When to use composition

@@ -15,7 +15,7 @@ products:
 
 # Flow control steps [workflows-flow-control-steps]
 
-Flow control steps shape a workflow's logic. They decide what runs, what gets skipped, when the workflow loops, and where it pauses. 9.4 ships the full set of 8 step types: `if`, `foreach`, `while`, `switch`, `wait`, `loop.break`, `loop.continue`, and `waitForInput`.
+Flow control steps shape a workflow's logic. They decide what runs, what gets skipped, when the workflow loops, and where it pauses. Workflows include 8 flow-control step types: `if`, `foreach`, `while`, `switch`, `wait`, `loop.break`, `loop.continue`, and `waitForInput`.
 
 ## When to reach for each
 

@@ -18,7 +18,7 @@
 Streams action steps operate on Observability [Streams](/solutions/observability/streams/streams.md) from a workflow. Use them to list available streams, fetch a specific stream's configuration, or pull significant events from a stream's time window.
 
 :::{warning}
-Streams action steps, along with the Streams feature itself, are in technical preview in 9.4. Schemas and semantics can change in future releases. Use these steps for prototypes and investigation workflows; hold off on critical automation until Streams reaches GA.
+Streams action steps, along with the Streams feature itself, are in technical preview. Schemas and semantics can change in future releases. Use these steps for prototypes and investigation workflows; hold off on critical automation until Streams reaches GA.
 :::
 
 ## Step types