Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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.

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 Future consideration
Categories Inflight
Created by Guest
Created on Nov 30, 2022

Restarting a Carbon Copy Branch in InFlight

We work on a lot of Business scenarios for the SCBN Customers where the main document is carbon copied and sent for parallel processing. In this case, we would see a separate entry for the main branch and separate entries for the Carbon Copied branches in InFlight.

The issue arises when one or all the Carbon Copy entries fail in InFlight on translation step or some other processing step while the actual Main branch gets successfully processed and delivered to the Customer or the Trading Partner.

In case, we have to just restart the Carbon Copy branches, it would restart the entire process and the main branch would get processed and delivered again thus causing duplication on the receiving side.

Can the InFlight tool provide an option to just restart the Carbon Copy branch ( that has failed) without re-triggering the other branches as those already got successfully processed?

What is your industry? Non-Industry Specific
How will this idea be used?

This enhancement would save duplication of files on the receiving party side and also save the IBM Implementers and Support teams from configuring rules for manual processing that are not required. Also, this would be a good to have feature as the Carbon Copy branches are shown as separate entries in InFlight so we should be able to restart them independently without triggering the main branch or other branches.