Timeouts from the InventoryTransfer endpoint

[Kjetil Ringstad]

Hi

The last few days inventory transfers through /controller/api/v1/inventoryTransfer results in timeout error messages returned from the API gateway.

The request itself does not time out, but the timeout message is being returned.

Can you please look into it? 

Example, company id 2693113 , today 19.08.2021 10:16:35 , payload:

{"warehouseId":{"value":"1"},"toWarehouseId":{"value":"1"},"transferLines":[{"toLocationId":{"value":"GA-16-05"},"operation": "Insert","inventoryNumber":{"value":"23420"},"locationId":{"value":"VM-00-00"},"quantity":{"value": 11},"uom":{"value":"STK"}}],"hold":{"value":false},"externalReference":{"value":""},"description":{"value":""}}

[schimmel-hsleiden]

Hi Magnus,

Thanks you for the answer and good that you are monitoring.

Kind regards,

Frank

[Yıldırım]

Thank you for the feedback !

[Steinar Møller]

Hi,
We have the same issue and it's really critical. We see this in several endpoints, Inventory, SalesPrice, Customer, SalesOrder etc.
Hope this will be solved as soon as possible. Thanks.

Log from system errors since last 
 03:59 31.08 5102 03:20 31.08 5102 og timeout 23:18 30.08 5102 22:41 30.08 5102 22:23 30.08 5102 21:06 30.08 5102 20:38 30.08 5102 19:47 30.08 5102 19:30 30.08 5102 16:20 30.08 5520 og {"message":"VismaId: 97fe0349-e41f-411e-a5fd-b01c1abeaf54. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"} og 502 bad gateway.

We also have the issue with not getting any response when we are posting, missing 201 request. Reported earlier. this has now been a problem for 2-3 weeks. 

Ex errors:
/controller/api/v1/Inventory?attributes=%7B%22BUTIKK3%22%3A1%7D&availabilityLastModifiedDateTimeCondition=%3E&availabilityLastModifiedDateTime=2021-08-31 01:49:46&pageNumber=1 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_a9279539-a9be-4059-856c-c191c838d45c","ExceptionDetails":""}

/controller/api/v1/customer?status=Active&corporateId=986503781&pageNumber=1 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_69533f9a-384c-4351-b8a8-4caae57365df","ExceptionDetails":""}


 

[Magnus Johnsen]

Hi,

We have increased the capacity of the servers handling the API traffic and the response time should now be far less and no longer be an issue.
We are still investigating the root cause of the increase in response time and will still be monitoring this.
Please let us know if you are still having the same issue with:

• Timeouts
• Missing response
• Connection closed

Thank you!

[Steinar Møller]

Hi.

Good neews. We have got no errors related to this so far today. We will continue monitoring. 

Brgds Steinar

[Roland van Belle - Consolit]

I have a reply from our customer.

They don't get a time-out anymore today!

Good news. We will monitor it for the next few days.

[Magnus Johnsen]

Hi Steinar,

That is also a case that is currently with the development team, I'll forward your comments to the case and ask for an update. 

[Roland van Belle - Consolit]

We have the same problem in our software on the same end-point.

Our customer compains about performance on this end-point. We wait till we have a response, so our customer see a message 'In progress'.

We will folow this post.

[Magnus Johnsen]

Hi,

Are all calls failing or only some?
Would you mind sharing CompanyID and some timestamps so we can check the logs?
Thank you. 

[Roland van Belle - Consolit]

CompanyID 3286391

Timestamp: 19-08-2021 9:41

Not all calls fail. But we have some timeouts. Before yesterday we did not ever have these timeouts.

[Magnus Johnsen]

Hi Kjetil,

Would you mind sending us the error message and confirm that it is not timeing out on your end?

The calls we see in our logs around that time are not failing, but they have a response of about 2 mins, where as most of your calls have a response time of about 1 min.

[Kjetil Ringstad]

I've received feedback from our customers that when releasing shipments this is happening as well. 

This has increased in occurences after last upgrade. 

[Kjetil Ringstad]

I don't have the raw JSON response at the moment, but  the response text itself is " Error receiving data: (12002) The operation timed out". As far as we have been able to track it's not timing out on our end.

[Magnus Johnsen]

Ok, thank you for the information, we are looking into it.

[Kjetil Ringstad]

Hi, another update as promised.

From Aug 5th we see timeouts starting, occuring more often from then 9th and from the middle of the month several occurences, and increasing.

[Magnus Johnsen]

Hi,

Ok, thank you I'll forward this to the development team.

It seems like it a general issue, we have reported several similiar cases to the development teams with critical priority.

[Roland van Belle - Consolit]

Hi,

Thank you for the update. Our customers have the time out several times a day.

It really is a critical issue.