When a lambda throws an error to indicate failure, it looks like the Step Functions task always assigns the error code “Exception” to it regardless of the exception type. I think this makes it impossible to route custom errors through the Retry and Catch handlers. Is there any way around this?
Thank you for reporting this. Starting from version 4.0.3, this issue should largely be resolved. Could you kindly confirm whether it addresses the problem you were experiencing?