Skip to Main Content
Digital Business Automation Ideas

This is an IBM Automation portal for Digital Business Automation products. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on May 13, 2022

Unattended Bot Scheduler is unreliable​, and should work without failures showing clear logging to increase confidence

The scheduler is not reliable. It uses an asynchronous process. As a result, we need to wait until the "trigger event" to know if it worked or not. Because it is asynchronous, we have no confirmation of any error when scheduling an unattended bot. That has resulted in major silent outages when there is a product defect, and reliably causes recreatable problems when there is a network issue. Let's say you try to create a scheduler in an offline machine, it should tell you right away that the machine is offline and unreachable. Instead, it fails when I try to create the scheduler and instead tells me at the time of the scheduler.​ We do not have confirmation that the item has been put on the schedule => we do not have the confirmation that the job has reached the Client machine. Even when it reaches the client, and even if the client acknowledges it, it can still fail once the time to start it arrives, as only then does the computer put in the queue. Improvements: - When we create a scheduler, we should get the notification right away if the target machine hasn’t received it. - If the target machine has connection to the api, but not to the queue, it should cancel/fail the scheduler right away, and not only at the time of the trigger - We need an easy way to track the connection between the client and the server, so we can properly investigate why schedulers fail. Right now we need to change the log to info, wait for it to happen again, and track connect/disconnect events. - If we have a clear description on when the connection was lost, and when it was returned, we can quickly check with IBM if there was infrastructure problems or determine if the error was in our own local network. - We need an easy way to track that all the needed API endpoints for IBM RPA are accessible and reachable. Right now we need to either guess, or run a curl on every single endpoint listed on IBM's documentation. If an endpoint that it’s needed for a feature is offline, said feature should have been blocked to the user.
Idea priority High
    Dec 15, 2022

    Following the Project and Bot concepts introduced in 23.0.0 release, we plan to build new features around bots and scheduling is one of the next items in our planning. The scheduler experience will be new and the current experience for scripts will be deprecated. The Product team considers this idea as not under consideration since we're working on a new experience to manage scripts and bots.