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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Spectrum Symphony
Components Version 7.1
Created by Guest
Created on Mar 4, 2016

[Workload Scheduling Policy][WellsFargo]Task redundant scheduling on timeout

Please advise how to implement the following functions:

1, have task timeout for 500 seconds.
2, if a task run more than 500 seconds, reschedule the task on a new
engine, but in the mean time, keep the original task running
3, for the original task running, and the newly re-scheduled task
running, whichever comes back first, send back to the client
4, for the second task run to complete, simply discard that task result
(or even cancel the second run upon receiving the result from first run)

  • Guest
    Dec 8, 2020

    .The solution with existing function, can be using application service control code to force the task rerun if it has been running for longer than expected (or any other instances). We do recognize the potential value of the required "redundant scheduling" of a task, however there is no short or mid term plan to include this in production as a common required case.

  • Guest
    Mar 6, 2017

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    Mar 1, 2017

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    Mar 9, 2016

    We have put this feature request into the Symphony backlog for consideration in a future release. We agree there is value in providing this functionality as part of the product offering in the future.

  • Guest
    Mar 5, 2016

    Creating a new RFE based on Community RFE #84913 in product Platform Symphony.