Instability from the API today and yesterday

[Steinar Møller]

We are getting several of network related errors. 

Some examples:

5520
/controller/api/v1/paymentMethod/

VismaId: ece112bd-14fd-4796-973c-5592ed1d1723. 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)
/controller/api/v1/Inventory

"Error creating shipment. The default configuration value for configuration key: PublicActiveMqURI is missing
/controller/api/v2/salesorder/b64(MTAwMDQ4OTY4NQ)/action/createShipment

[Magnus Johnsen]

Hi,

How frequently has this been happening?

Is it happening for all endpoints or some specifically?

Thank you.

[andreasaulin]

More errors today:
We do see quite a few different errors regarding things not working as it should in the API

New for today is
{"message":"Connection to cache service failed"}
Different endpoints and clients

"ExceptionFaultCode":"5520"
Different endpoints and clients

"exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'."
Different enpoints and clients

and in addition timeouts from time to time (we are waiting 30 seconds for a reply)

[Yıldırım]

Hello, we've informed the infrastructure team regarding this. Could you please inform us on the company ID that you receive the mentioned error ?