Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Created by Guest
Created on Feb 16, 2026

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