Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 (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
  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.


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.


Status Not under consideration
Workspace Rational Other
Categories Build Forge
Created by Guest
Created on Dec 3, 2013

Restarting broadcast step pick up failed server

Restarting broadcast step picks up random server rather than failed server. One of purpose of using broadcast is to run a step at all matching servers. However, failed step randomly select a server based on selector rule. As a result of this behavior, broadcast step did not run at all matching server, and of cause some servers ran the step multiple times after restarting it.

It would be great if restarting broadcast step has an option that can use all previously assigned servers and do not use selector rule again.

Idea priority Medium
RFE ID 42395
RFE URL
RFE Product Rational Build Forge
  • Guest
    Sep 15, 2022

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, aged or been delivered, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Build Forge

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Product & application lifecycle management
    Product - Build Forge

  • Guest
    Jul 21, 2014

    change it to un-commit condidate state

  • Guest
    Jul 3, 2014

    agreed that there are some valuable use cases where the selector should not be re-evaluated but the broadcast steps themselves (chlidren of the broadcast) should be restarted

  • Guest
    Apr 29, 2014

    This RFE is consistent with our strategy and product roadmap and IBM is continuing to evaluate.