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.


Add a new idea Subscribe
Status Submitted
Workspace API Connect
Created by Guest
Created on Sep 22, 2026

RELATED IDEAS

Add a distinct ConnectionTimeout error to the Invoke policy to differentiate timeouts from other ConnectionError failures

In IBM API Connect, Invoke policy timeout failures are reported under ConnectionError, making it difficult to distinguish timeouts from other connectivity failures in assembly catch blocks.

Please introduce a dedicated, catchable ConnectionTimeout error for Invoke timeout failures, while retaining ConnectionError for other connection failures.

Expected behavior:

  • Allow ConnectionTimeout to be selected in the Invoke policy’s stop-on-error configuration and handled separately in assembly catch blocks.
  • Expose structured details identifying whether the timeout occurred during connection establishment or while waiting for the backend response.
  • Make this distinction available without requiring developers to parse error-message text.
  • Preserve existing error-handling behavior through an opt-in setting or a new policy version.

This would help API developers and production support teams implement accurate error responses, map timeouts to HTTP 504 where appropriate, and distinguish backend delays from connectivity issues in monitoring and troubleshooting.

Idea priority High

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.