Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Mar 4, 2026

Tool calls should have individual configurable timeouts

Currently all tool calls in WxO have a timeout of 2 minutes. This is not configurable at all in Cloud, and in order to configure it in CP4D you must change the timeout for *all* tool calls in the WxO deployment as well as configure timeouts for other components accordingly.

Customer has some remote MCP servers built on Langflow whose running time often exceeds 2 minutes. They want Builders be able to easily adjust the timeouts for these tools on an individual basis according to their expected running times and not require the WxO cluster Admin to make deep configuration changes.

Idea priority High