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 Submitted
Categories Global Mailbox
Created by Guest
Created on Jun 11, 2024

B2Bi Sterling Integrator generating invalid delivery status in the application UI following deadlock

In April 2024 an external client submitted a payment file into the B2Bi Sterling Integrator product within my production environment.  The file routed and delivered successfully to the remote target system, and the payment file processed through the environment. However, during the delivery process there was a Database deadlock which prevented some of the internal business processes from completing. 

In the delivery tab, the FileGatewaySendMessage errored, and the file status in the Out of the Box UI was marked as "Failed" as a result of a Database deadlock which occurred whereby two SQL IDs were updating the same record in the database concurrently. 

In this particular scenario, the the file status was marked as failed which was incorrect, despite the deadlock, why would the product mark the file as "failed", could a more appropriate status be applied e.g. determining or delivering? The failed status caused confusion within the production environment and led to a client level impact.