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 Apr 29, 2026

Implement rate limiting (1.2/3) - size of incoming and outgoing requests

wxO is used externally in B2C mode, asking for rate limiting for several aspects :

- Security, to avoid a DoS attack and wxO to become less responsive,
- Consumption, avoiding consuming too many token, and having a too long conversation to redirect,

Details : Checks on the size of incoming and outgoing requests, implement strict size limits on the size of incoming and outgoing requests

  • Explicitly configure a maximum number of tokens in API calls to the AI model to force the text generation to stop once a reasonable volume is reached (e.g., 1,000 tokens per response).

These point concerns both API and UI.

Idea priority Urgent
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    May 13, 2026

    Looking into this but a custom way to handle it today is using plugins to check size of request in input and output: https://developer.watson-orchestrate.ibm.com/plugins/plugins