The Custom Error Categorization feature should work beyond Run steps
M
Mint Locust
https://developer.harness.io/continuous-integration/3.0/use-harness-ci/use-harness-ci/custom-error-categorization currently only supports run steps.
There are lots of common errors that teams run into that are not in run steps but would benefit greatly from a custom error message.
For example, users might run an input set designed for a trigger manually, or force push to a repo during a pipeline run break a clone step. The errors presented to users in these scenarios are obtuse, and would benefit greatly from custom error messages that provide concrete resolution steps.
However, they are stage errors or errors in steps other than "Run" steps, so we cannot add custom messages as the Custom Error Categorization feature is currently designed.