Skip to content

docs: document workflow loop guardrails#7097

Open
rosomri wants to merge 2 commits into
mainfrom
docs/workflow-loop-guardrails
Open

docs: document workflow loop guardrails#7097
rosomri wants to merge 2 commits into
mainfrom
docs/workflow-loop-guardrails

Conversation

@rosomri

@rosomri rosomri commented Jun 24, 2026

Copy link
Copy Markdown

Summary

  • Document loop-level guardrails for foreach and while workflow steps: max-iterations, timeout, on-failure, and if.
  • Document iteration-level guardrails: iteration-timeout and iteration-on-failure.
  • Update the flow-control overview and error-handling restrictions so they align with the new loop guardrail behavior.

Testing

  • Checked diagnostics for the edited docs files with ReadLints.
  • Reviewed the final git diff before committing.

Document loop-level and iteration-level safety controls for foreach and while workflow steps.
@rosomri rosomri requested review from a team as code owners June 24, 2026 09:08
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


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.

@charlotte-hoblik charlotte-hoblik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, 🙂 clean change, and the applies_to tagging is spot on. I left a few inline suggestions.

One thing that's better as a manual move than a suggestion:

Could we move the ## Guardrails section to sit between ## Context variables and ## Example? Where it is now, its ga 9.4+ badge also covers the pre-9.4 "expression types" intro that follows it.

Comment thread explore-analyze/workflows/steps/foreach.md Outdated
Comment thread explore-analyze/workflows/steps/flow-control-steps.md Outdated
Comment thread explore-analyze/workflows/steps/flow-control-steps.md Outdated
Comment thread explore-analyze/workflows/steps/while.md Outdated
Apply review feedback to clarify loop guardrail references and keep overview docs concise.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants