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 (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.

Add a new idea Subscribe
Status Submitted
Workspace Sterling B2B Integration SaaS
Categories Inflight
Created by Guest
Created on Oct 15, 2025

RELATED IDEAS

Display Protocol Delivery Failure Error Details in InFlight Event Details

When a file fails to get delivered via SFTP, AS2, etc. after the retry limit gets exhausted, we just see some basic details in the Event details of the "Retry Limit" step in InFlight as shown below.


Reached retry count limit -

Retry Count Limit: 5

Retry Start Alert Count: 4

Retry Interval: 900 seconds

Retry Time Limit: 432000 seconds

Session ID: 77dc39b7-2919-4219-8323-321c899fa0b2

Session Ended: Tue Oct 14 04:48:56 EDT 2025

Retry Started: Tue Oct 14 03:36:11 EDT 2025

Retry Ended: Tue Oct 14 04:48:56 EDT 2025

Current Retry Count: 5

Process ID: 721202467

In order to get the details of the actual error, we need to login to the respective POD (say POD41 for SFTP, POD40 for AS2, etc) and then search with the Process ID to get the details of the error. This is how it shows on POD.


Status Report:

SFTPClientBeginSession failed.
Error Message = [Cannot authenticate.: ]
SFTPClientAdapter=[BPN_SFTP_CLIENT_ADAPTERS]
ServiceStartTime =[2025-10-14 04:48:51.227]
ServiceEndTime = [2025-10-14 04:48:56.008]
Time taken to complete the Service is 4.781 Seconds
SessionToken=[BPN_SFTPClientAdapter_SFTPClientAdapter_node1_176043173122771364:551027007]


Please provide the error details available on Protocol POD in InFlight event details of the "Retry Limit" failed step so that we can come to know straight away the reason for the failure. Even Client would get an understanding of why the file could not be delivered.


Also, the Process ID on Protocol POD is just available for 5 days and in case we need to check the error details of a file which got failed to deliver before the 5 days time frame, there is no option to do so.

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

This would save a lot of time in debugging as the Implementer or the Support person will not have to login on the Protocol POD to check for the failure details. In case we are facing issues with delivery of files via SFTP or AS2, etc. and we or Client/Trading Partner are working on fixing the issue which requires trying to send the file multiple times, the availability of the error details in InFlight would be helpful rather than we searching for the details on the Protocol POD with the PID that is provided in event details.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.