API Karate tests are failing because of modules failure

Overview:

A lot of API Karate tests are failing.

Upon review - the failure is not related to any functional issues, but caused by modules failure while running the pipeline, timeouts, etc.

For example:

• response: proxyClient failure: mod-orders-12.1.0-SNAPSHOT.418 http://10.36.10.83:9225: finishConnect(..) failed: Connection refused: /10.36.10.83:9225: POST /orders/composite-orders

- com.intuit.karate.exception.KarateException: create-order-with-invoice-that-has-enough-money.feature:215 -
java.net.SocketTimeoutException: Read timed out

- com.intuit.karate.exception.KarateException: exchange-rate-update-after-invoice-approval.feature:176 - status code was: 500, expected: 204, response time: 158, url: http://ec2-54-80-232-188.compute-1.amazonaws.com:9130/invoice/invoices/a199c594-d649-42d0-9ff3-a45300697adc, response: {"total_records":1,"errors":[{"code":"genericError","message":"{\n \"errors\" : [

{\n \"message\" : \"Internal Server Error\",\n \"code\" : \"genericError\",\n \"parameters\" : [ ]\n }

],\n \"total_records\" : 1\n}","parameters":[]}]}

As a result the Cucumber report is not reliable as it shows a lot of failures, though no fixes are required on Development Teams' side.