[Workflows] Authoring, monitoring/troubleshooting, and managing

[nastasha-solomon]

Summary

Fixes the following issues:

• [Internal][Workflows][9.3 & Serverless][Phase 1]: YAML-based authoring experience #4651: Describes the YAML editor interface, which you use to create, run, and validate workflows.
• [Internal][Workflows][9.3 & Serverless][Phase 1]: Execution and debugging  #4656: Describes how to monitor executed workflows and troubleshoot failures.
• [Internal][Workflows][9.3 & Serverless][Phase 1]: Managing workflows #4655: Explains how to manage workflows from the Workflows page.

Previews

• Author workflows
• Monitor and troubleshoot workflows
• Manage workflows

To find these pages in the left nav, go to Elastic Docs > Explore and analyze > Workflows

NOTE:

• These previews are static deployments generated via netlify – they won't get auto-updated when new commits are pushed to the PR.
• These previews are deployments of the Explore and analyze section – pages outside of this section are not available to preview.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Cursor, claude-4.5-opus-high

[github-actions]

Vale Linting Results

Summary: 3 suggestions found

💡 Suggestions (3)

File	Line	Rule	Message
explore-analyze/workflows/author-workflows.md	13	Elastic.Repetition	"to" is repeated.
explore-analyze/workflows/manage-workflows.md	13	Elastic.Repetition	"to" is repeated.
explore-analyze/workflows/monitor-troubleshoot.md	13	Elastic.Repetition	"to" is repeated.

---

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.

[jamesspi]

@nastasha-solomon the pre-requisites section under authoring is missing RBAC. We also make no mention of complete or the actions menu (maybe this should also be on the actions section).

I would also highlight the quick-copy step name from the output viewer as a very helpful tip for workflow authoring.

[jamesspi]

We should also highlight that we include an indication of a test run vs a production run (the beaker means test run).

[nastasha-solomon]

Hey, @jamesspi a few follow-up questions:

We also make no mention of complete or the actions menu (maybe this should also be on the actions section).
The Actions menu is briefly described here. What other information should be included in the description?

I would also highlight the quick-copy step name from the output viewer as a very helpful tip for workflow authoring.

Can you elaborate on how this would be used in workflow authoring? For example, would users use the copy option to access the output of a specific field that returns data for a step? Also, I'm wondering if this tip would be better suited in the data docs, perhaps here?

We should also highlight that we include an indication of a test run vs a production run (the beaker means test run).

I don't think I've seen the "test run" and "production run" terms defined in the One Workflow google doc. If they're described there, can you point me towards the info? If not, how would you define these terms?

[nastasha-solomon]

Additional changes to this content can be made in #4758.