Context
Currently, all exceptions thrown as part of the unsafe flow process are categorized as "server errors" (or just "Failure") in the subscription trigger history. Some cases of unsafe flow exception are clearly a repo / codeflow configuration issue, and not an error in the processing itself.
Goal
Turn all the unsafe-flow related configuration exceptions into "User errors", and make sure they have clear and helpful exception messages attached.
Context
Currently, all exceptions thrown as part of the unsafe flow process are categorized as "server errors" (or just "Failure") in the subscription trigger history. Some cases of unsafe flow exception are clearly a repo / codeflow configuration issue, and not an error in the processing itself.
Goal
Turn all the unsafe-flow related configuration exceptions into "User errors", and make sure they have clear and helpful exception messages attached.