-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Document Fix with AI for failed workflow steps #39218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -55,11 +55,25 @@ | |
| The initial run history for a workflow provides a panel with the list of previous workflow executions and whether each execution succeeded or failed. Failures include a link to the failed workflow step. Click on a workflow execution in the list to inspect it. You can return to the initial execution history at any time by clicking anywhere on the workflow canvas. | ||
|
|
||
|
|
||
| ## 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. | ||
|
|
||
| {{< 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
|
|
||
| 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
|
|
||
| If the failed step triggers another workflow, debug the triggered workflow's own run history to find the underlying failure. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
|
|
||
|
|
||
| ## Further reading | ||
|
|
||
| {{< partial name="whats-next/whats-next.html" >}} | ||
|
|
||
| <br>Do you have questions or feedback? Join the **#workflows** channel on the [Datadog Community Slack][10]. | ||
|
|
||
| [6]: /actions/workflows/expressions/ | ||
| [7]: /bits_ai/bits_chat/ | ||
| [10]: https://chat.datadoghq.com/ | ||
There was a problem hiding this comment.
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.