Skip to content

Document Fix with AI for failed workflow steps - #39218

Draft
nhrsh wants to merge 2 commits into
masterfrom
neha/workflow-automation-fix-with-ai
Draft

Document Fix with AI for failed workflow steps#39218
nhrsh wants to merge 2 commits into
masterfrom
neha/workflow-automation-fix-with-ai

Conversation

@nhrsh

@nhrsh nhrsh commented Aug 16, 2026

Copy link
Copy Markdown

Add a section to the Test and debug page describing how to use the Fix with AI action to resolve a failed workflow step.

What does this PR do? What is the motivation?

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

Add a section to the Test and debug page describing how to use
the Fix with AI action to resolve a failed workflow step.
@github-actions

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@github-actions github-actions Bot added the Images Images are added/removed with this PR label Aug 16, 2026
@nhrsh
nhrsh requested a review from GabeWM August 16, 2026 17:14

## Fix a failed step with AI

From a failed step's error message in {{< ui >}}Run History{{< /ui >}}, click {{< ui >}}Fix with AI{{< /ui >}} to get help resolving the failure.

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.

Your image doesn't actually use a failed steps view, it uses workflow output view.


{{< img src="actions/workflows/test_and_debug/fix-with-ai.png" alt="Bits Chat diagnosing and proposing a fix for a failed workflow step." >}}

The assistant opens in [Bits Chat][7], diagnoses the failure using the step's inputs, outputs, execution context, and error message, and can search external documentation for errors returned by third-party APIs. It explains the issue and proposes a fix. Unless you turn on {{< ui >}}Auto-approve{{< /ui >}}, the assistant waits for your confirmation before applying any change. After you confirm, the assistant updates the step's configuration and reruns validation.

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.

This is not true, very silly and I have shared the feedback with Bits Chat, but auto approve has no effect on MCP tools. Only UI tools.


The assistant opens in [Bits Chat][7], diagnoses the failure using the step's inputs, outputs, execution context, and error message, and can search external documentation for errors returned by third-party APIs. It explains the issue and proposes a fix. Unless you turn on {{< ui >}}Auto-approve{{< /ui >}}, the assistant waits for your confirmation before applying any change. After you confirm, the assistant updates the step's configuration and reruns validation.

Fixes with AI apply to problems in the workflow's configuration, such as incorrect inputs or an outdated action setup. The assistant can't fix failures caused by external factors, such as invalid credentials, rate limits, or outages in a connected service. Investigate those with the owner of the connected service.

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.

I don't know if I would phrase it as this, it can tell you what you need to fix on those sites. It kinda feels like this discourages the user of the feature.


Fixes with AI apply to problems in the workflow's configuration, such as incorrect inputs or an outdated action setup. The assistant can't fix failures caused by external factors, such as invalid credentials, rate limits, or outages in a connected service. Investigate those with the owner of the connected service.

If the failed step triggers another workflow, debug the triggered workflow's own run history to find the underlying failure.

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.

I'd be curious if you tested this. I think it may just work now with the toolset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants