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.

Add idea Subscribe
Created by Guest
Created on Feb 16, 2026

RELATED IDEAS

Remove or increase the Scheduler repeat limit (currently capped at 100)

Watsonx Orchestrate Scheduler currently has a hard limit of 100 repeats per scheduled task. For production deployments where agents or flows need to run on a recurring basis (e.g. daily), this means the schedule silently expires after approximately 3 months, requiring a manual re-configuration.

Current workaround: Manually re-scheduling the agent/flow every time it reaches the 100-repeat cap. This is unsustainable for production environments and introduces risk of downtime if the expiry goes unnoticed.

Proposed solution: Either remove the repeat limit entirely or significantly increase it (e.g. 10,000+), with an option for indefinite scheduling. An optional notification before a schedule expires would be very helpful.

Benefits: Enables clients to rely on scheduled agents for ongoing automated workflows without manual intervention. Without this, the Scheduler cannot be used in production.

Users impacted: In our case, this directly impacts client deployments that depend on continuous automated workflows.

Idea priority Medium
  • Post comment

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.