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 Not under consideration
Created by Guest
Created on Jun 9, 2025

Enable Rest API resources to invoke async flow service

Currently, a defined Rest API resource against a flow service only makes use of the synchronous interface. The intent here is be able to choose which flow service interface to use - i.e. the private synchronous or the private asynchronous interface in the API resource definition. 

Our goal is to enable an asynchronous API to our consumers and ensure that any subsequent failure in the implementation service is properly manageable (via flow restart functionality).

Our best option today is to have a synchronous API with a messaging queue as the intermediate storage to support the asynchronous behavior. But even here, we are unable to restart a failed flow service that acts as a messaging subscriber (separate Idea has been submitted).

 

Idea priority Medium
  • Admin
    John Carter
    Jul 3, 2025

    Thank you for your submission, but as you state we async APIs can be orchestrated via messaging and the issue with being able to resubmit failed services is under review.

    Hence I will close this idea.