Known issues and limitations

Get a quick overview of the known issues and limitations for IBM watsonx Orchestrate ADK.

Issue	Description
`orchestrate --version` command	`orchestrate --version` command might not work or return the wrong version. To solve it, run `which orchestrate` to ensure it’s using your Python virtual environment (venv); if not, remove conflicting versions until it does, and if the issue persists even with the correct venv, delete and recreate the venv and reinstall the ADK.
Tool import after upgrade	If you upgraded your watsonx Orchestrate Developer Edition and try to import a tool, you might run into permission issues. Run `docker volume rm docker_tools-runtime-data` to remove the existing tools and trigger a clean reinstall.
MCP tool upload	When you upload MCP tools from the filesystem, you must zip the tool folder. You should be able to point to the root folder instead, but that isn’t working as expected.
Renaming tools	When a tool name is modified within watsonx Orchestrate, the change is not propagated back to MCP. Currently, tool updates are unidirectional, flowing only from MCP to watsonx Orchestrate. As a result, any renaming or updates made in watsonx Orchestrate will not be reflected in MCP, potentially leading to inconsistencies or communication issues between the two systems.
Tool flow	If you delete an OpenAPI tool from the CLI and then import the same tool again, tool flow fails. The re-imported tool gets a different tool ID, so it no longer matches the original reference.