The problem getting the request Id in the instance of timeout is that no response is provided from Visma. I performed another test at: 2020-08-31T12:00:29.377+02:00 Two salesOrder POST requests was tried, when one of two failed. The request ID for the successfull one is 928a724c-eb18-43e4-8ed3-a0c86f1f9456. The other one at this timestamp timed out. The exception message: Failed to send SalesOrder to Visma with message 'I/O error on POST request for \"https://integration.visma.net/API/controller/api/v1/salesorder\": timeout; nested exception is java.net.SocketTimeoutException: timeout'" Error HTTP Response with status: 504, body: null Body of the failed request: {\"currencyId\":{\"value\":\"NOK\"},\"lines\":[{\"operation\":\"insert\",\"inventoryNumber\":{\"value\":\"P-208\"},\"quantity\":{\"value\":6.0}}],\"customer\":{\"value\":\"DAM10206\"},\"orderType\":{\"value\":\"SO\"},\"date\":{\"value\":\"2020-08-11\"}} Yes I have implemented a retry function that handles exceptions of type HttpStatusCodeException, but this timeout returns IOException, and I can not be sure if the request is processed by Visma. How I handle this at the moment, is to just accept this timeout for POST requests, and continue. This way all requests (so far) has ended up in Visma, but This is not a robust solution.
... View more