Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Apr 7, 2017

IMS Rep: maintain/reset error status for subscriptions

There have been times when a subscription had an error that resulted in the subscription stopping, but also resulted in the started task crashing. When automation restarts the task, the errored subscription is now in an "inactive" status, in spite of the server producing a WTO identifying it as having failed, just like all the other subscriptions that we are currently in the process of setting up or had intentionally stopped.

However, there are times that an error occurred that we have resolved but we don't want to restart and then stop the subscription to clear the error status.

Please maintain the unhealthy status of errored/failed subscriptions across restarts of the started task instead of switching to a generic "inactive". Similarly, provide a command to clear an error state to "inactive"