Skip to Main Content
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



Status Future consideration
Created by Guest
Created on Jul 21, 2025

Granular and actionable error logs & chat messages

We encountered a scenario where a user had configured the Agent to connect to a tool that triggered a Python script. While the Agent was connected, it suddenly stopped responding and displayed the following error message:

"I'm sorry, it seems I've encountered an error calling the tool. Error in Python tool execution: failed to update due to {'error': 'failed to execute function in Pod: API returned status 500'}"

Upon reviewing the logs from the tool_runtime_manager container, it was determined that the root cause was a timeout error.

If this timeout information had also been surfaced in the chat window, it would have provided the user with a clearer indication that the issue was related to a connection timeout—helping them better understand and potentially resolve the problem more efficiently.

Idea priority High
  • Guest
    Sep 2, 2025

    Hi! I’m experiencing a similar issue 🥲

    For the past two weeks, I’ve been trying to run a Python-based tool in watsonx Orchestrate, but I keep getting this error:

    "I have encountered an error calling the tool. Please try again. Error Details: Error getting Python tool status: Error getting Python tool status. The pod is starting up, please try after some time."

    It seems like the pod is stuck in a CrashLoopBackOff state. I’ve already opened a support case, but I haven’t received a resolution yet.

    Honestly, it’s been an odyssey trying to develop tools—sometimes they work, sometimes they don’t. I usually record videos of the chat when it works, because it might suddenly stop responding right before a live demo. Right now, I can’t even use the tools at all.

3 MERGED

Instead of 504 errors, concise errors should be surfaced to the user, instead of having to dig through CP4D/vLLM logs

Merged
"Instead of 504 errors, if it's something surfaced from vLLM like: 2025-08-22T00:41:31.362506975Z ERROR 08-22 00:41:31 [serving_chat.py:200] ValueError: This model's maximum context length is 128000 tokens. However, you requested 844373 tokens (84...
3 months ago in IBM watsonx Orchestrate 0 Future consideration