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 Planned for future release
Created by Guest
Created on Jan 24, 2024

Failed Outbound exchanges should be retried

A previous RFE requested a solution to retry outbound AS4 one way push exchange where the failure was caused by a HTTP 30xm 40x or 50x error.  This was implemented and is working well. This has saved us considerable time and expense by not requiring the execution of daily reconciliations to identify initiated exchanges that have failed to deliver successfully.  Further refinement of our configured RETRY POLICY or the Conformance Policy configurations has also reduced the number of outbound failures that are not automatically retried.

However, it has been identified that there are other scenarions where IBM B2B Advanced Communications does not attempt to retry failed outbound AS4 One way push exchanges.  This issue was raised under support case  TS011023954  Created on  Oct 25, 2022 12:28 GMT+10.


On Oct 18, 2023, 15:28, the support team finally responded with the following - 


     -Had a discussion in our meeting , explained following

      Delivery retry can happen on two cases . 1. on socket timeout error 2. customer configured http error codes where retry exception thrown. However in this particular scenario           "" there is no retry possible in the code and transaction is failed . This is as per design.

      -Please raise a ER if you need retry to be done for "" t



As an ebMS/AS4 gateway administrator I want to see all failed exchanges retried regardless of the reason for failure - the lack of a receipt is a key indicator of failure.  


As per previous comments, Failed outbound messages are only identified after exhaustive manual reconciliations across various messages types and patterns.  This takes operational support staff at least 1 hour every business day to complete the reconciliations and then additional time to actually take action to restart/replay/resend any identified messages.

The solution to retry failed exchange by restarting/replaying from within B2Bi is not a valid solution because, time still needs to be expended to identify the failed exchanges.

The business impact is that the Precision Administration Gateway is failing to meet message SLA with reportable breaches occurring regularly - perticularly where messages fail outside business hours.

It would be ideal if these failed message scenarios could be identified and leverage the Conformance Policy "no receipt received" message retry approach.



  • Admin
    Mark Allen
    Apr 17, 2024

    Thank you for taking the time to provide your ideas to IBM. Your request may not be delivered within the release currently under development, but the theme aligns with our current roadmap and, as such, is being tagged for future consideration. IBM may consider and evaluate any community feedback for your request through activities such as voting and we may reach out to you about this request to discuss additional details with you in the future.

    We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

    If you have any additional feedback or thoughts, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.

    Please note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion.