Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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 idea Subscribe
Status Future consideration
Created by Guest
Created on Jul 21, 2025

RELATED IDEAS

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
  • Post comment
  • 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.

    Reply
4 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...
2 months ago in  0 Future consideration

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.