[One Workflow] Implement outputs, workflow.output and workflow.fail steps by VladimirFilonov · Pull Request #253700 · elastic/kibana

VladimirFilonov · 2026-02-18T12:02:00Z

Summary

Adds support for workflow outputs, the workflow.output step, and the workflow.fail step — enabling workflows to declare structured outputs, emit values at runtime, and terminate with a failure status.

This is part of Workflow Composition, extracted as a standalone deliverable without dependency on workflow.execute.

What's included

Schema & Types (@kbn/workflows)

New outputs top-level field on the workflow definition schema (WorkflowOutput[])
New WorkflowOutputStepSchema (workflow.output) and WorkflowFailStepSchema (workflow.fail) step types
output field added to WorkflowContextSchema and DynamicWorkflowContextSchema for variable access ({{ output.fieldName }})
WorkflowSchemaForAutocomplete updated to include outputs for editor tooling

Execution Engine

workflow.output step implementation that emits structured outputs and terminates execution
workflow.fail step (internally transformed to workflow.output with status: 'failed')
setWorkflowOutputs, setWorkflowStatus, and completeAncestorSteps on the runtime manager for early termination
Execution graph builder handles workflow.output and workflow.fail node types

Editor & Autocomplete

Context-aware autocomplete for the with: block of workflow.output steps — suggests declared output field names from the workflow's outputs definition
Position-based fallback detection for cases where the YAML parser returns an empty path (cursor on blank lines inside with:)
YAML provider suppression when inside workflow.output's with: block to prevent generic JSON Schema suggestions from leaking through
Dynamic snippet generation for workflow.output (pre-fills with block from declared outputs) and workflow.fail
output variable autocomplete ({{ output.fieldName }}) with type-aware schema derived from declared outputs

Validation

validateWorkflowOutputs — validates declared outputs definitions (types, constraints, naming)
validateWorkflowOutputsInYaml — validates workflow.output steps' with: blocks against declared outputs schema
Generic validateWorkflowFields utility for reusable Zod-based field validation

Tests

Schema tests for WorkflowOutputSchema, WorkflowOutputStepSchema, WorkflowFailStepSchema
Integration tests for workflow.fail execution
Validation tests for validateWorkflowOutputs (352 lines covering all output types and constraints)
Autocomplete integration tests for workflow.output with: block suggestions

Test plan

Example

name: Fail
enabled: true
description: This is a new workflow
triggers:
  - type: manual

inputs:
  - name: fail
    type: boolean
    default: false

outputs:
  - name: result
    type: string
  
steps:
  - name: if
    condition: "intpus.fail: true"
    steps:

      - name: success
        type: workflow.output
        with:
          result: "success"
    else:
      - name: fail
        type: workflow.fail
        with:
          message: "Ooops"

Copilot

Pull request overview

This PR implements workflow outputs functionality, enabling workflows to declare structured output fields, emit values at runtime, and terminate execution with specific status codes.

Changes:

Added outputs top-level field to workflow schema with validation for string, number, boolean, choice, and array types
Implemented workflow.output and workflow.fail step types with execution engine support
Enhanced editor autocomplete to suggest declared output fields within workflow.output steps' with: blocks

Reviewed changes

Copilot reviewed 30 out of 30 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
validate_workflow_outputs.ts	Delegates output validation to shared field validator
validate_workflow_outputs.test.ts	Comprehensive validation tests for all output types and constraints
validate_workflow_fields.ts	Generic Zod-based validator shared between inputs and outputs
generate_connector_snippet.ts	Updated to use centralized `isBuiltInStepType` helper
generate_builtin_step_snippet.ts	Added snippet generation for `workflow.output` and `workflow.fail` steps
get_workflow_outputs_suggestions.ts	Context-aware autocomplete for output field names in `workflow.output` steps
get_suggestions.ts	Refactored suggestion logic to support workflow output autocomplete
get_connector_type_suggestions.ts	Updated to pass workflow outputs for dynamic snippet generation
variable.test.ts	Added integration tests for workflow output autocomplete
get_completion_item_provider.ts	Suppresses YAML provider suggestions inside `workflow.output` with blocks
autocomplete.types.ts	Changed workflowDefinition type to WorkflowYaml for better type safety
get_workflow_context_schema.ts	Builds output schema from declared outputs for variable autocomplete
validate_workflow_outputs_in_yaml.ts	Validates `workflow.output` steps against declared outputs schema
use_yaml_validation.ts	Integrates workflow output validation into YAML validation pipeline
workflow_execution_state.ts	Fixed merge logic to avoid overwriting defined fields with undefined
workflow_execution_runtime_manager.ts	Added methods for setting outputs, status, and completing ancestor steps
step_execution_runtime.ts	Made workflowExecution getter public and improved type safety
build_workflow_context.ts	Added `output` field to workflow context
workflow_output_step_impl.ts	Core implementation of workflow.output step with validation and termination logic
nodes_factory.ts	Added factory method for workflow.output node creation
workflow_fail.test.ts	Integration tests for workflow.fail step execution
schema.ts	Added WorkflowOutput, WorkflowOutputStep, and WorkflowFailStep schemas
schema.test.ts	Schema validation tests for workflow output step types
generate_yaml_schema_from_connectors.ts	Registered new step types in YAML schema generation
base.ts	Added WorkflowOutputGraphNode type
build_execution_graph.ts	Added graph building logic for workflow.output and workflow.fail steps

...ws_management/public/widgets/workflow_yaml_editor/lib/validation/validate_workflow_fields.ts

...hared/workflows_execution_engine/server/workflow_context_manager/workflow_execution_state.ts

...red/workflows_execution_engine/server/step/workflow_output_step/workflow_output_step_impl.ts

rosomri

Nice work on the outputs implementation! 👑

One design observation: outputs currently only support the legacy array format ([{ name, type, required }]), while inputs already support both legacy and JSON Schema formats with automatic normalization.

If outputs followed the same pattern (normalize to JSON Schema at parse time via .transform() like inputs do), the existing utilities (convertLegacyInputToJsonSchemaProperty, normalizeInputsToJsonSchema, convertJsonSchemaToZod) could replace the three custom output-to-Zod implementations (makeOutputValidator, makeWorkflowFieldsValidator, outputToSchema/buildOutputsSchema), cutting ~400 lines of new code and keeping inputs/outputs architecturally consistent.

That said, if adding JSON Schema support for outputs is a larger design change that you see as out of scope for this PR, I’m fine moving forward as-is. I just wanted to flag the opportunity - aligning with the input pipeline would give you JSON Schema support and shared utilities essentially for free down the line.

...ws_management/public/widgets/workflow_yaml_editor/lib/validation/validate_workflow_fields.ts

rosomri · 2026-02-18T12:31:57Z

...s_management/public/features/validate_workflow_yaml/lib/validate_workflow_outputs_in_yaml.ts

+
+  const stepsSeq = stepsNode as YAMLSeq;
+
+  for (const stepNode of stepsSeq.items) {


Note, this only iterates top-level steps items. workflow.output steps nested inside if or foreach blocks will not be validated by the editor

Added recursion in validate_workflow_outputs_in_yaml.ts: collectFromStepsSequence() traverses nested steps and else in if/foreach.

talboren · 2026-02-18T13:23:15Z

...form/plugins/shared/workflows_execution_engine/integration_tests/tests/workflow_fail.test.ts

@@ -0,0 +1,314 @@
+/*


There are thorough integration tests for workflow.fail, but no integration test for workflow.output with status: 'completed' (the happy path). The schema tests validate parsing, but they don't verify runtime behavior: outputs stored in context.output, workflow status is COMPLETED, subsequent steps are NOT executed.

Consider adding a workflow_output.test.ts alongside this file covering: basic output emission, output validation against declared schema, early termination (steps after workflow.output should not run), and type-preserving template expressions.

Added workflow_output.test.ts (basic emission, early termination, templates, workflow.output inside if).

talboren · 2026-02-18T13:25:45Z

...red/workflows_execution_engine/server/step/workflow_output_step/workflow_output_step_impl.ts

+
+          // Fail the step with the error
+          // Note: failStep() already sets the workflow error, so we don't need to call setWorkflowError() separately
+          this.stepExecutionRuntime.failStep(failureError);


failStep() only sets the step-level error (on the step execution document), not the workflow-level error. This means workflowExecution.error won't be populated with the failure message.

The validation failure path (line ~180) and catch block (line ~274) both call setWorkflowError() explicitly after failStep(). This branch should do the same for consistency:

this.stepExecutionRuntime.failStep(failureError); this.workflowExecutionRuntime.setWorkflowError(failureError);

Also, the comment on line 234 should be updated since it's incorrect.

@VladimirFilonov let me know if I'm misunderstanding the flow here - is there maybe error propagation happening elsewhere that covers this case?

failStep() already calls updateWorkflowExecution({ error }). I removed redundant setWorkflowError() from validation and catch paths;

VladimirFilonov · 2026-02-23T12:12:26Z

That said, if adding JSON Schema support for outputs is a larger design change that you see as out of scope for this PR, I’m fine moving forward as-is. I just wanted to flag the opportunity - aligning with the input pipeline would give you JSON Schema support and shared utilities essentially for free down the line.

Acknowledged as future improvement - will create follow-up ticket for that

...red/workflows_execution_engine/server/step/workflow_output_step/workflow_output_step_impl.ts

…d schema validations

…r template syntax

…e proper step completion and error reporting

…low-output-and-fail

src/platform/packages/shared/kbn-workflows/spec/schema.ts

...red/workflows_execution_engine/server/step/workflow_output_step/workflow_output_step_impl.ts

...agement/public/features/validate_workflow_yaml/lib/use_monaco_markers_changed_interceptor.ts

...agement/public/widgets/workflow_yaml_editor/lib/autocomplete/get_completion_item_provider.ts

src/platform/packages/shared/kbn-workflows/spec/lib/build_zod_schema_from_fields.ts

src/platform/plugins/shared/workflows_management/common/lib/json_schema_to_zod.ts

…low-output-and-fail

src/platform/plugins/shared/workflows_execution_engine/server/utils/templates.ts

rosomri

Several call sites need explicit casts:

load_workflows_thunk.ts: workflow.definition?.inputs as NormalizableFieldSchema
validate_json_schema_defaults.ts: inputs as NormalizableFieldSchema
workflow_execute_modal.tsx: inputs as NormalizableFieldSchema
workflow_output_step_impl.ts: declaredOutputs as NormalizableFieldSchema

This suggests the upstream types (WorkflowYaml.inputs, WorkflowYaml.outputs) don't align with NormalizableFieldSchema. Consider widening the WorkflowYaml type to make inputs and outputs typed as NormalizableFieldSchema | undefined so these casts become unnecessary.

src/platform/packages/shared/kbn-workflows/spec/lib/build_fields_zod_validator.test.ts

rosomri · 2026-03-12T13:41:09Z

...s_management/public/features/validate_workflow_yaml/lib/validate_workflow_outputs_in_yaml.ts

+      const stepType = getStepType(stepNode);
+      if (stepType === 'workflow.output') {
+        collectWorkflowOutputStepFromNode(stepNode, items, model);
+      } else if (stepType === 'foreach' || stepType === 'if') {


Not all cases are covered - what about on-failure/timeout/while steps?

Also, each new step would need to be explicitly added here, which is fragile at best and essentially broken.

Instead, could the steps be flattened somehow, instead of traversing the DAG? The graph structure doesn’t really matter anyway.

https://github.com/elastic/kibana/pull/253700/changes#r2925014657 - can fix it as well

rosomri · 2026-03-12T13:46:06Z

...s_management/public/widgets/workflow_yaml_editor/lib/validation/validate_workflow_outputs.ts

+export function makeWorkflowOutputsValidator(outputs: NormalizableFieldSchema) {
+  return makeWorkflowFieldsValidator(outputs);
+}


nit - Why not call makeWorkflowFieldsValidator directly?

rosomri · 2026-03-12T13:46:58Z

...rm/plugins/shared/agent_builder/server/services/tools/tool_types/workflow/generate_schema.ts

@@ -54,7 +57,9 @@ export const generateSchema = ({ workflow }: { workflow: WorkflowDetailDto }): z
  }

  // Normalize inputs to the new JSON Schema format (handles backward compatibility)
-  const normalizedInputs = normalizeInputsToJsonSchema(workflow.definition.inputs);
+  const normalizedInputs = normalizeFieldsToJsonSchema(
+    workflow.definition.inputs as NormalizableFieldSchema


needed? you already overcome it

Suggested change

workflow.definition.inputs as NormalizableFieldSchema

workflow.definition.inputs

rosomri · 2026-03-12T14:00:12Z

WorkflowOutputGraphNodeSchema missing from GraphNodeUnionSchema.
The new WorkflowOutputGraphNodeSchema is defined in base.ts and exported, but it was not added to the discriminated union in union.ts.
Add WorkflowOutputGraphNodeSchema to the GraphNodeUnionSchema array in union.ts, and optionally add an isWorkflowOutput guard in guards.ts.

rosomri · 2026-03-12T14:03:33Z

...s_management/public/features/validate_workflow_yaml/lib/validate_workflow_outputs_in_yaml.ts

+ * Reads the outputs section from the raw YAML document as a plain object.
+ * Used when workflowDefinition.outputs is missing (e.g. schema parse stripped it).


I don't really get the usecase and why a fallback is needed instead of relying on the 'outputs' only, but anyway, the logic only recognizes the JSON Schema format. If outputs are declared in the legacy array format (which is valid per WorkflowOutputSchema = WorkflowInputSchema), this fallback won't detect them

Documented the fallback use case in JSDoc - we use it when workflowDefinition.outputs is missing (e.g. parse failure or definition not yet available) so we can still validate workflow.output steps from the raw YAML.
I think it's valid, since workflow.outputs allow any amount for extra keys, not described in schema. So it's fare to assume that it can be none + extra fields

Fallback now supports legacy array format as well: if the raw document has outputs: [{ name, type, ... }], we return it and normalizeFieldsToJsonSchema handles it. Added a test for the legacy fallback path.

rosomri · 2026-03-12T14:21:19Z

...s_management/public/features/validate_workflow_yaml/lib/validate_workflow_outputs_in_yaml.ts

+/**
+ * Recursively collects workflow.output steps from a steps sequence (including nested if/foreach).
+ */
+function collectFromStepsSequence(


The manual recursive traversal (getStepType, findNestedStepsSequence, collectFromStepsSequence, collectWorkflowOutputSteps) reimplements logic that already exists in common/lib/yaml/get_step_nodes_with_type.ts. That utility uses visit() to walk the entire YAML AST and collect all step nodes at any nesting depth - it already handles if, foreach, while, etc.
You could replace the ~60-80 lines of traversal code with:

import { getStepNodesWithType } from '../../../../common/lib/yaml/get_step_nodes_with_type'; const allStepNodes = getStepNodesWithType(yamlDocument); const outputStepNodes = allStepNodes.filter((node) => { const typePair = node.items.find( (item) => isPair(item) && isScalar(item.key) && item.key.value === 'type' ); return isPair(typePair) && isScalar(typePair.value) && typePair.value.value === 'workflow.output'; });

rosomri · 2026-03-12T14:45:45Z

...rkflow_yaml_editor/lib/autocomplete/suggestions/workflow/get_workflow_outputs_suggestions.ts

@@ -0,0 +1,269 @@
+/*


The functions findStepIndexAtPosition, getStepTypeFromIndex, stepHasWithProperty, and isInWorkflowOutputWithBlock manually scan YAML lines to determine if the cursor is inside a workflow.output step's with: block. But focusedStepInfo from the autocomplete context already provides this - it's derived from the YAML AST and handles nesting correctly.

This whole chain could be replaced with:

focusedStepInfo?.stepType === 'workflow.output'>

This is the same approach used in get_workflow_inputs_suggestions.ts (line 117), which checks focusedStepInfo?.stepType === 'workflow.execute' without any custom line scanning.

Bonus: findStepIndexAtPosition only checks top-level steps, so autocomplete inside nested blocks likely won't trigger. focusedStepInfo handles those correctly.

rosomri · 2026-03-15T11:13:36Z

Icon is missing

Output field autocomplete in the with: block is currently suggested on the same line as with, which results in invalid YAML if selected. It should be consistent with the rest of the editor and only provide suggestions on the line below.

All output types are currently completed as strings, regardless of their actual type. This lead to invalid YAML and results in a poor UX.

Autocompletion doesn't work for jsonSchema

Shouldn’t the output be presented under the trigger section?

Wrong execution logo

rosomri · 2026-03-16T15:09:47Z

..._management/public/features/workflow_execution_detail/ui/workflow_step_execution_details.tsx

              ) : (
                <>
                  {selectedTabId === 'output' && (
-                    <>


You sure these are not needed anymore?

Yes, this is wrong callout for Output: "You can reference these values using {{ inputs. }}"

It's just an accidental leftover

…low-output-and-fail

elasticmachine · 2026-03-17T08:13:47Z

💚 Build Succeeded

Buildkite Build
Commit: 0b06ff0

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`agentBuilder`	1781	1782	+1
`cases`	2073	2084	+11
`genAiSettings`	659	670	+11
`securitySolution`	9177	9188	+11
`workflowsExtensions`	311	312	+1
`workflowsManagement`	1282	1287	+5
`workplaceAIApp`	1049	1060	+11
total			+51

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/workflows`	487	497	+10

Any counts in public APIs

Total count of every any typed public API. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats any for more detailed information.

id	before	after	diff
`@kbn/workflows`	115	120	+5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`workflowsManagement`	1.8MB	1.8MB	+8.2KB

Unknown metric groups

API count

id	before	after	diff
`@kbn/workflows`	579	592	+13

ESLint disabled line counts

id	before	after	diff
`workflowsManagement`	107	106	-1

Total ESLint disabled count

id	before	after	diff
`workflowsManagement`	143	142	-1

History

…teps (elastic#253700) ## Summary Adds support for **workflow outputs**, the **`workflow.output`** step, and the **`workflow.fail`** step — enabling workflows to declare structured outputs, emit values at runtime, and terminate with a failure status. This is part of [Workflow Composition](elastic/security-team#14633), extracted as a standalone deliverable without dependency on `workflow.execute`. ### What's included **Schema & Types (`@kbn/workflows`)** - New `outputs` top-level field on the workflow definition schema (`WorkflowOutput[]`) - New `WorkflowOutputStepSchema` (`workflow.output`) and `WorkflowFailStepSchema` (`workflow.fail`) step types - `output` field added to `WorkflowContextSchema` and `DynamicWorkflowContextSchema` for variable access (`{{ output.fieldName }}`) - `WorkflowSchemaForAutocomplete` updated to include `outputs` for editor tooling **Execution Engine** - `workflow.output` step implementation that emits structured outputs and terminates execution - `workflow.fail` step (internally transformed to `workflow.output` with `status: 'failed'`) - `setWorkflowOutputs`, `setWorkflowStatus`, and `completeAncestorSteps` on the runtime manager for early termination - Execution graph builder handles `workflow.output` and `workflow.fail` node types **Editor & Autocomplete** - Context-aware autocomplete for the `with:` block of `workflow.output` steps — suggests declared output field names from the workflow's `outputs` definition - Position-based fallback detection for cases where the YAML parser returns an empty path (cursor on blank lines inside `with:`) - YAML provider suppression when inside `workflow.output`'s `with:` block to prevent generic JSON Schema suggestions from leaking through - Dynamic snippet generation for `workflow.output` (pre-fills `with` block from declared outputs) and `workflow.fail` - `output` variable autocomplete (`{{ output.fieldName }}`) with type-aware schema derived from declared outputs **Validation** - `validateWorkflowOutputs` — validates declared `outputs` definitions (types, constraints, naming) - `validateWorkflowOutputsInYaml` — validates `workflow.output` steps' `with:` blocks against declared outputs schema - Generic `validateWorkflowFields` utility for reusable Zod-based field validation **Tests** - Schema tests for `WorkflowOutputSchema`, `WorkflowOutputStepSchema`, `WorkflowFailStepSchema` - Integration tests for `workflow.fail` execution - Validation tests for `validateWorkflowOutputs` (352 lines covering all output types and constraints) - Autocomplete integration tests for `workflow.output` `with:` block suggestions ## Test plan - [ ] Verify `outputs` field is accepted in workflow YAML definitions - [ ] Verify `workflow.output` step emits outputs and terminates execution - [ ] Verify `workflow.fail` step terminates with failed status - [ ] Verify autocomplete suggests declared output names inside `workflow.output`'s `with:` block - [ ] Verify autocomplete filters out already-provided output keys - [ ] Verify `{{ output.fieldName }}` variable autocomplete works with correct types - [ ] Verify validation errors for invalid output definitions - [ ] Verify validation errors when `workflow.output` `with:` block doesn't match declared outputs - [ ] Run `yarn test:jest src/platform/plugins/shared/workflows_management/ --no-coverage` - [ ] Run `yarn test:jest src/platform/packages/shared/kbn-workflows/ --no-coverage` ## Example ```yaml name: Fail enabled: true description: This is a new workflow triggers: - type: manual inputs: - name: fail type: boolean default: false outputs: - name: result type: string steps: - name: if condition: "intpus.fail: true" steps: - name: success type: workflow.output with: result: "success" else: - name: fail type: workflow.fail with: message: "Ooops" ``` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

VladimirFilonov requested a review from a team as a code owner February 18, 2026 12:02

botelastic bot added the Team:One Workflow Team label for One Workflow (Workflow automation) label Feb 18, 2026

VladimirFilonov added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Feb 18, 2026

talboren requested a review from Copilot February 18, 2026 12:18

Copilot AI reviewed Feb 18, 2026

View reviewed changes

rosomri reviewed Feb 18, 2026

View reviewed changes

This comment was marked as outdated.

Sign in to view

talboren reviewed Feb 18, 2026

View reviewed changes

talboren changed the title ~~Implement outputs, workflow.output and workflow.fail steps~~ [One Workflow] Implement outputs, workflow.output and workflow.fail steps Feb 19, 2026

VladimirFilonov requested review from rosomri and talboren February 23, 2026 12:19

github-advanced-security bot found potential problems Feb 23, 2026

View reviewed changes

...red/workflows_execution_engine/server/step/workflow_output_step/workflow_output_step_impl.ts Fixed Show fixed Hide fixed

VladimirFilonov added 4 commits March 4, 2026 13:53

Implement outputs, workflow.output and workflow.fail steps and relate…

1856100

…d schema validations

address review comments

0b27d68

Enhance workflow output step validation by ensuring minimum length fo…

0a48f18

…r template syntax

Update error handling in workflow output step implementation to ensur…

5e59574

…e proper step completion and error reporting

VladimirFilonov force-pushed the feature/14634-workflow-output-and-fail branch from 4a6049f to 5e59574 Compare March 4, 2026 09:57

kibanamachine and others added 3 commits March 4, 2026 10:14

Changes from node scripts/eslint_all_files --no-cache --fix

31f8c7d

drop unused outputToSchema

b799357

Add JsonSchema support for workflow.output step

00b288f

VladimirFilonov requested a review from a team as a code owner March 9, 2026 10:41

Merge remote-tracking branch 'upstream/main' into feature/14634-workf…

8fec4a8

…low-output-and-fail

rosomri reviewed Mar 9, 2026

View reviewed changes

VladimirFilonov added 2 commits March 11, 2026 13:49

Adressing comments

2bb3434

Merge remote-tracking branch 'upstream/main' into feature/14634-workf…

b79aa94

…low-output-and-fail

github-advanced-security bot found potential problems Mar 11, 2026

View reviewed changes

src/platform/plugins/shared/workflows_execution_engine/server/utils/templates.ts Fixed Show fixed Hide fixed

rosomri reviewed Mar 11, 2026

View reviewed changes

rosomri reviewed Mar 12, 2026

View reviewed changes

src/platform/packages/shared/kbn-workflows/spec/lib/build_fields_zod_validator.test.ts Show resolved Hide resolved

rosomri reviewed Mar 12, 2026

View reviewed changes

Merge branch 'main' into feature/14634-workflow-output-and-fail

9c9c063

rosomri reviewed Mar 12, 2026

View reviewed changes

VladimirFilonov added 2 commits March 12, 2026 21:17

Address more comments

a024491

Merge branch 'main' into feature/14634-workflow-output-and-fail

bdfac66

rosomri mentioned this pull request Mar 15, 2026

[One Workflow] Add loop.break and loop.continue loop flow control steps #255835

Merged

VladimirFilonov added 6 commits March 15, 2026 20:11

Merge branch 'main' into feature/14634-workflow-output-and-fail

84b8ba0

Add icons for output/fail and update icons for execute

a603eb0

adjust autocomplete on with:

6891efd

Better autocomplete type suggestions

951d5d7

Show output on trigger node in history UI

ea90029

Add tests

33c5d6d

rosomri reviewed Mar 16, 2026

View reviewed changes

rosomri approved these changes Mar 16, 2026

View reviewed changes

Merge remote-tracking branch 'upstream/main' into feature/14634-workf…

c7b0d5d

…low-output-and-fail

VladimirFilonov enabled auto-merge (squash) March 16, 2026 16:00

VladimirFilonov added 2 commits March 17, 2026 11:07

Temporary backward compatibility for agent-builder

5095d84

Merge branch 'main' into feature/14634-workflow-output-and-fail

0b06ff0

VladimirFilonov merged commit 13a9816 into elastic:main Mar 17, 2026
18 checks passed

kibanamachine added the v9.4.0 label Mar 17, 2026


		const stepsSeq = stepsNode as YAMLSeq;

		for (const stepNode of stepsSeq.items) {

	workflow.definition.inputs as NormalizableFieldSchema
	workflow.definition.inputs

		* Reads the outputs section from the raw YAML document as a plain object.
		* Used when workflowDefinition.outputs is missing (e.g. schema parse stripped it).

Conversation

VladimirFilonov commented Feb 18, 2026

Summary

What's included

Test plan

Example

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rosomri left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

talboren Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

VladimirFilonov commented Feb 23, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rosomri left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rosomri commented Mar 12, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rosomri commented Mar 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

elasticmachine commented Mar 17, 2026

💚 Build Succeeded

talboren Feb 18, 2026 •

edited

Loading