Skip to Main Content
Integration


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 (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 Submitted
Workspace App Connect
Created by Guest
Created on Oct 14, 2025

Ability to Suspend a flow at the point of failure and resume it from that point onwards.

Problem Statement:
Using the default behaviour of Record/Replay feature of IBM ACE , exceptions are recorded in the configured database but to replay from the point of failure will need to add Queues equivalent to Number of Message Flows multiplied by the No of Point of Failures. In a large implementation this is not a feasible approach.

Expectation for Enhancement:
Considering the recorded message has the point of failure on replay the execution of node should start from the node where exception had started using only one replay queue per message flow. The status of replay should be captured and should not be available for replay if teh replay execution was successful.

The Web UI should have provision to create custom filters for the display of failed tranactions application wise which can be saved and access can be provided to operations users for retry as required.

Idea priority Urgent