What do you dislike about IBM watsonx Orchestrate?
1- Reports
Lack of clear and detailed reports on usage, performance, and failures.
Hinders the analysis of metrics for decision-making.
2- Graphical Flow
Confusing and unintuitive visuals in larger flows.
Does not facilitate quick identification of discrepancies between steps.
3- Debug
Limited debug tool, lacking clarity on what was evaluated.
Hinders error traceability and understanding of flow behavior.
4- Limited Expressions
Lack of support for more advanced expressions.
Problems in evaluating variables (e.g., boolean values or data concatenation).
5- Integrations
Integration with APIs is not very flexible.
Inconsistent returns (partial vs. complete JSON) require manual solutions.
6- Passing Variables Between Steps
Difficulty in retrieving variable values (blank latitude/longitude).
Inconsistency in accessing step.body in different contexts.
7- Inconsistent Step Behavior
Steps calling the same API may have different results without clear explanation.
Excessive reliance on internal IDs instead of transparent logic.
8- Inability to Reuse Steps
It is not possible to copy steps from one flow and paste them into another.
Generates rework in dialogue construction and hinders standardization.
9- Tool Deployment
Publishing process is not intuitive.
Lack of clarity about environments (test vs. production).
Slow deployment with little control over rollback. Review collected by and hosted on G2.com.