Building tools: Known issues
Review known issues and limitations that affect tool creation, agentic workflows, and tool execution.
At a glance
|
Issue |
Workaround available |
|---|---|
|
No |
|
|
Yes |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
In IBM Cloud environments, users might not appear in the User field of a form in chat |
Yes |
|
User trigger field mapping does not work for progressive selection |
Yes |
Async tool support
Currently, watsonx Orchestrate does not support asynchronous Python tools end-to-end. When a custom tool is designed to run asynchronously, such as using threading or asyncio to handle concurrent tasks, the system does not properly await its response.
Tool execution fails to invoke the tool
Tool execution fails on the first attempt to invoke the tool and succeeds during the second attempt on the same thread.
Workaround: If you encounter a failure after a prolonged period of inactivity, retry the execution once.
Multi-file upload tools with ReAct style agents
Multi-file upload tools are not supported with ReAct style agents. Use the default agent style for multi-file upload functionality.
Unable to scroll the extracted fields
If you add up to 25 fields in the document extractor, the scroll bar is not displayed, preventing you from viewing all the extracted fields.
Preview of send for human review in flows
Previewing the send for human review in document processing is not supported.
Optional model support
The optional meta-llama/llama-3-2-11b-vision-instruct model for document extractor and document classifier is not supported in certain regions (Asia Pacific (AP) South and Tokyo).
For more information, see Regional availability of provided foundation models.
Default inputs used in a nested agentic workflow
The expected behavior is that the engine prompts the user to provide inputs to the tool if they cannot be computed. However, instead of a prompt, a default value is used.
If there are no inputs in the parent workflow that can automatically map to the inputs of the tools, or if there are no user activity nodes collecting relevant inputs to the tool, the workflow calls the tool using automapping and generates default inputs for the tool.
Workaround: To pass specific values or null values for these inputs, they must be explicitly modified in the data mapping.
Agent fails to deploy
An agent fails to deploy if it includes a workflow that was created previously in the technology preview.
Workaround: Open the workflow in the agentic workflow builder and edit the name or description and save it. Saving the workflow updates the workflow configuration to work with the general availability release.
Agentic workflow input date format
For date input fields, you must provide date inputs in ISO format only (yyyy-mm-dd).
Workaround: If the input is not in ISO format, the workflow returns an error. Ensure that all date inputs follow the ISO format.
Observability
The system does not currently include the agentic workflow runtime events in observability traces when the workflow is not associated with an agent. For example, this occurs when you initiate an agentic workflow through the Flow APIs.
For more information about observability, see Monitoring agents.
In IBM Cloud environments, users might not appear in the User field of a form in chat.
This issue occurs because the platform APIs required to list users must be explicitly authorized on IBM Cloud.
Workaround: To enable user listing, the Watson Orchestrate tenant administrator must create either a Service ID or a user with the appropriate IBM Cloud platform permissions.
Required IAM permissions
Assign the following roles:
-
Administrator role: Assigned to the Service ID. Scoped to the target Watson Orchestrate tenant as the resource.
-
Viewer role: Assigned for all IAM account management services.
The administrator must register the API key associated with the Service ID or user as a connection using the predefined application ID WXO_PLATFORM_USER_API. Refer to the following commands:
$ orchestrate env activate
$ orchestrate connections add -a WXO_PLATFORM_USER_API
$ orchestrate connections configure -a WXO_PLATFORM_USER_API --env draft -t team -k api_key
$ orchestrate connections configure -a WXO_PLATFORM_USER_API --env live -t team -k api_key
$ orchestrate connections set-credentials -a WXO_PLATFORM_USER_API --env draft --api-key
$ orchestrate connections set-credentials -a WXO_PLATFORM_USER_API --env live --api-key
After these steps are completed, the platform APIs can successfully retrieve users, and they appear in the User field within a chat.
User trigger field mapping does not work for progressive selection
When you map inputs using user trigger fields, progressive selection in dynamic forms does not work.
Work around : Use auto-mapping, which is the default, instead of mapping from user trigger fields.
Related information