We’ve been working closely with Moveworks Support and Engineering and wanted to share some feedback regarding process timeouts in Agent Studio 2.0.
Background:
- In Agent Studio Classic / 1.0, compound actions allow for asynchronous API calls. Each action within a compound action has a 60-second timeout, but there’s no overall timeout for the compound action itself. This has enabled us to build plugins that perform multiple API calls efficiently.
- In Agent Studio 2.0, conversational process replaces compound actions. However, the process is synchronous, and there’s a 60-second timeout for the entire conversational process.
Issue: We’re encountering PLUGIN_ERROR_TIMEOUT in 2.0 like a user in this thread is experiencing:
The suggested workaround from Moveworks Engineering is to use a compound action within the conversational process, allowing us to run actions asynchronously OR to just use compound action for the entirety of this plugin. We cannot optimize / use faster APIs to avoid timeout thresholds entirely due to our security architecture.
Concern: While this workaround technically resolves the timeout issue, it seems to defeat the purpose of migrating to 2.0 for processes that require multiple long API calls. The synchronous nature of conversational processes in 2.0 limits us compared to the flexibility we had in 1.0. Additionally, if we need input validation of 2.0, then we must use conversational process + compound action which gets difficult to manage.
Request: Is there any discussion internally of either increasing the timeout threshold beyond 60 seconds for conversational processes, or to enable (even specific actions within) conversational processes to be asynchronous?
Currently, the main advantage we see in 2.0 is input validation, data types, and UI, while 1.0 remains more flexible for most workflow requirements.
