This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Currently when testing any workflow for e.g. authentication failure, the logs are not verbose enough to show details of failure nor the details of API's calls being made. This makes it difficult to identify what is contributing to the failure. |
Idea priority | Medium |
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.
@Guest We've reviewed this with the Engineering team and there is not a way forward with this Idea that preserves the security of the secrets we store in the product. Secret security is a pillar of our design.
When unexpected or incorrect behaviors occur in the product with any integration, please bring this to the attention of the Support team.
How can a user sort out the difference between a working curl command and a failing block?
More trace level detail visibility still needed beyond what core dump can show.
Some integrations are unusable without directly referencing the vendor documentation. These integrations also do not provide any information about the payload structure and whether or not the payload would match the documented structure.
Ask is to be able to see headers, body, etc in the requests that blocks send.
Any errors or situations like this that arise in the integrations should be reported as bugs. These should be fixed so that they "just work" or so that there is enough information provided in the UI to make them work.
2. There is a "core dump" log level that can be engaged in the settings. Gear icon >> System Configuration >> General Settings >> On Error Behavior
This will return the full state of all variables and blocks when an exception happens in a flow
3. The risk we would introduce with increasing the verbosity is that the trace data returned can expose secret credential information. On of the key tenets of the product is that that situation should be impossible.