Request for explicit error type in error messages and better error type documentation
long-term
P
Plum Butterfly
It would be great if the error type would be explicitly exposed in the error message in case of a failure during pipeline execution.
For example:
[TimeoutError] Steady state check failed with error: error: deployment "unit" exceeded its progress deadline
instead of simply
Steady state check failed with error: error: deployment "unit" exceeded its progress deadline
Also the documentation on the error types is very minimal https://developer.harness.io/docs/platform/pipelines/failure-handling/define-a-failure-strategy-on-stages-and-steps/#error-types It would be great if you can add an exhaustive list of exact error conditions for each error type.
Log In
Rohan Gupta
Merged in a post:
Capture and display rich error messages in stderr
O
Opera mauve Wren
We need the standard error (stderr) stream to display rich error messages and ensure these are captured in the pipeline execution log files. This enhancement would help us determine the health of our system more effectively.
Autopilot
Merged in a post:
Clear error messages for pipeline reconciliation
T
Turquoise Loon
When reconciling pipelines, the error messages provided are not clear enough to diagnose specific issues, especially when dealing with branch-specific templates. Improving the clarity of error messages would help users understand and resolve issues more efficiently.
Rohan Gupta
marked this post as
long-term
Yes we can improve our error messages to expose type, we will work with our team to improve the error documentation.