Skip to Main Content

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

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
Workspace App Connect
Created by Guest
Created on Dec 18, 2023

Add ability to Error Catch logic be added for Batch Flows in Designer Flows

In designer flows without a batch flow it is possible to add an Error Catch to the flow and within that error catch perform specific error handlng based on the information found in the Error Details object.  In flow with a batch flow included, the same Error Catch can be added but it only applies to errors that occur outside of the batch process.  


In many cases it is necessary to perform certain cleanup when an occurs within the batch flows as well as the non-batch parts of the flow.


My suggestion is to add a mechanism where either one error catch can be created to the enitre flow, both batch and non-batch, or to have seperated error catches that apply to each.



Idea priority High
  • Admin
    Ben Thompson
    Jan 15, 2024

    Idea review. Thank you very much for taking the time to raise this suggestion Jeff, which we're moving into Future Consideration status. We understand and agree on the use case of better facilities for catching and handling errors that occur within a batch process, but when it comes to precise implementation choices we want to also express a note of caution. When making changes in this area, we will want to be careful not to impair the simplicity of the Designer Programming model and also take care to maintain the distinctions we have with the Toolkit programming model (where rollback logic is implemented between nodes, Fail terminals are available on each node, TryCatch nodes can be used to isolate catch branches for specific sections of message flows, or a subflow concept is also available). Looking forward to hearing design thoughts from the community on this suggestion.