-
Notifications
You must be signed in to change notification settings - Fork 227
Agentic AI: Document known error codes #7174
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 7 additions & 0 deletions
7
...out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-codes-task.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| The AI Agent Task generates the following error codes when creating the tool schema from the process definition XML: | ||
|
|
||
| | Error code | Description | | ||
| | :----------------------------------- | :------------------------------------------------------------------------------------------------------- | | ||
| | `AD_HOC_SUB_PROCESS_XML_FETCH_ERROR` | The process definition XML could not be fetched. | | ||
| | `AD_HOC_SUB_PROCESS_NOT_FOUND` | The ad-hoc sub-process with the configured ID could not be found in the process definition XML. | | ||
| | `AD_HOC_TOOL_DEFINITION_INVALID` | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tool schema. | | ||
15 changes: 15 additions & 0 deletions
15
...s/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-handling.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,22 @@ | ||
| import ConfigurationErrorCodesTask from './\_error-codes-task.md'; | ||
|
|
||
| ### Error handling | ||
|
|
||
| If an error occurs, the AI Agent connector throws an error and includes the error response in the error variable in Operate. | ||
|
|
||
| | Field | Required | Description | | ||
| | :--------------- | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Error expression | No | You can handle an AI Agent connector error using an Error Boundary Event and [error expressions](/components/connectors/use-connectors/index.md#error-expression). | | ||
|
|
||
| In the error expression, you can handle the following error codes emitted by the AI Agent connector to respond to specific situations. For example, you can map a specific error code to a BPMN error and model | ||
| your process accordingly. | ||
|
|
||
| | Error code | Description | | ||
| | :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | `FAILED_MODEL_CALL` | The call to the LLM API failed, for example due to misconfiguration or wrong credentials. The error message contains additional details. | | ||
| | `FAILED_TO_PARSE_RESPONSE_CONTENT` | The AI Agent was configured to parse the LLM response as JSON, but the parsing failed. | | ||
| | `MAXIMUM_NUMBER_OF_MODEL_CALLS_REACHED` | The AI Agent reached the maximum number of configured model calls. | | ||
| | `NO_USER_MESSAGE_CONTENT` | Indicates that no user message content, either from a user prompt or a document, was provided to the agent. | | ||
afgambin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| | `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT` | Tool call results were passed to the AI Agent despite the context being empty, which typically indicates a misconfiguration of the agent context. | | ||
|
|
||
| {props.type === "task" && <ConfigurationErrorCodesTask />} | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 7 additions & 0 deletions
7
...out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-codes-task.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| The AI Agent Task generates the following error codes when creating the tool schema from the process definition XML: | ||
|
|
||
| | Error code | Description | | ||
| | :----------------------------------- | :------------------------------------------------------------------------------------------------------- | | ||
| | `AD_HOC_SUB_PROCESS_XML_FETCH_ERROR` | The process definition XML could not be fetched. | | ||
| | `AD_HOC_SUB_PROCESS_NOT_FOUND` | The ad-hoc sub-process with the configured ID could not be found in the process definition XML. | | ||
afgambin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| | `AD_HOC_TOOL_DEFINITION_INVALID` | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tool schema. | | ||
14 changes: 14 additions & 0 deletions
14
...s/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-handling.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,21 @@ | ||
| import ConfigurationErrorCodesTask from './\_error-codes-task.md'; | ||
|
|
||
| ### Error handling | ||
|
|
||
| If an error occurs, the AI Agent connector throws an error and includes the error response in the error variable in Operate. | ||
|
|
||
| | Field | Required | Description | | ||
| | :--------------- | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Error expression | No | You can handle an AI Agent connector error using an Error Boundary Event and [error expressions](/components/connectors/use-connectors/index.md#error-expression). | | ||
|
|
||
| In the error expression, you can handle the following error codes emitted by the AI Agent connector to respond to specific situations. For example, you can map a specific error code to a BPMN error and model | ||
| your process accordingly. | ||
|
|
||
| | Error code | Description | | ||
| | :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | `FAILED_TO_PARSE_RESPONSE_CONTENT` | The AI Agent was configured to parse the LLM response as JSON, but the parsing failed. | | ||
| | `MAXIMUM_NUMBER_OF_MODEL_CALLS_REACHED` | The AI Agent reached the maximum number of configured model calls. | | ||
| | `NO_USER_MESSAGE_CONTENT` | Indicates that no user message content, either from a user prompt or a document, was provided to the agent. | | ||
afgambin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| | `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT` | Tool call results were passed to the AI Agent despite the context being empty, which typically indicates a misconfiguration of the agent context. | | ||
|
|
||
| {props.type === "task" && <ConfigurationErrorCodesTask />} | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.