IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Under review
Workspace IBM watsonx Orchestrate
Created by Guest
Created on May 23, 2026

RELATED IDEAS

Enable HTTP Status Code Handling for Granular Error Management in Workflows

Currently, when using OpenAPI integrations in Watson Orchestrate workflows, all API errors are routed through a single default branch. This limits the ability to implement differentiated error-handling strategies based on the nature of the failure.

This enhancement would allow workflows to access and evaluate the HTTP status code returned by API calls, enabling more granular and intelligent decision-making within the orchestration logic.

Proposed behavior:

  • The HTTP status code should be exposed as part of the API response within the workflow.
  • Users should be able to define conditional branches based on status code ranges (e.g., 2xx, 4xx, 5xx).

Example use cases:

5xx errors (server-side issues):
Automatically trigger a fallback response informing the user to retry later, as the issue is likely temporary or external to the user’s input.

4xx errors (client-side issues):
Parse the error message and trigger specific failure scenarios. For instance:

  • Return a meaningful error message to the user
  • Redirect the workflow to a previous step
  • Allow the user to correct or adjust their input before retrying

Who benefits:

  • Developers building orchestrations with external APIs
  • Enterprises integrating mission-critical services where error handling impacts user experience
  • End users, by receiving clearer guidance instead of generic failures
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.