Currently, we don't handle the error produced from calling a non-existent lambda function gracefully. This isn't caught in our lambda_local js tests. This is most likely due to the lambda container running a successful dry run.