Review the fixes and limitations in Agent Interoperability for the v.40 release.

Fixes

Enterprise users no longer receive an error message when creating an inbound tool from an automation that uses the same variable for both input and output. Now, you can successfully create an inbound tool using the Agent Connections page, and the output details will show correctly in the GetAutomationResult tool.

Limitations

Limitations from previous releases
You must manually refresh or edit the agent connections whenever you update any automation. This includes changes such as enhanced descriptions or when you add, update, or remove any input/output variables.
The DiscoverAutomation tool might not work or behaves unexpectedly if a user has access to more than 1,000 folders in the repository. This happens because the API times out when handling so many folders. Besides the DiscoverAutomation tool not working, there are no other problems.
When a user uses the DiscoverAutomation tool on public automations, the system only checks the first 200 automations that the user can access. This is based on the permissions set for them in the automation repository. Any automations beyond first 200 will not appear in the DiscoverAutomation's tool search results. However, the user can set up these specific automations as individual agent connections and use them as separate automation tools.
Checked-in automations might take a while to be discovered. It can take 5-10 minutes to summarize the automation. This depends on how many tasks are checked in and how long it takes to create the summary for each automation.
You must delete the agent connections manually whenever the associated automation is deleted or when the user's access is revoked. The MCP client might take some time to remove or refresh the deleted or revoked automations from Tools list because of caching.