My Products
Help
Timo_O
CONTRIBUTOR ***

SalesOrder added via Api , despite response code 500

by Timo_O (Updated ‎09-03-2023 13:05 by Timo_O )

Hi,

yesterday 7.3. at 16:50 local Finnish time

 

we sent our customers salesorder request  via api :

POST  https://integration.visma.net/API/controller/api/v1/salesorder

 

As response we got:

HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 34a3a460-b31f-4a62-99b7-17fa8cb5a39c. Error communicating with message broker"}

 

Despite the error code, a new SalesOrder instance was added in Visma.net.

Due to the error message, our integration interpret that the request had not been received, and we resent  a duplicate order to customers Visma.net company.

Is this error 'Error communicating with message broker'
such that it always requires a closer check for success or failure?

 

Wbr,

Timo

 

2 REPLIES 2
Accepted solution
Magnus Johnsen
VISMA

by Magnus Johnsen (Updated ‎10-03-2023 11:49 by Magnus Johnsen VISMA )

Hi,

We recommend that you use the v2 of the salesOrder endpoint for posting your orders:

2023-03-10 11_46_38-Visma.net Integrations Documentation - Brave.png

We also recommend looking into the NextGen SalesOrder service as well.

Please update the endpoint to V2 and let us know if you are having the same issue.

For more information on the endpoints, please have a look at Swagger

Timo_O
CONTRIBUTOR ***

by Timo_O (Updated ‎10-03-2023 08:44 by Timo_O )

More information to this issue from our logs.
We have got this error code several times as response  with different customers in time gap 7.3. 16:52   -   8.3. 02:45.

In the same time there has been more succesfull requests with normal response.


Here under some examples.

The 2 first requests/messages  did add a new Salesorder in Visma.net to company 3502689.

The 5 later requests/messages  did not,   company for these requests is  2862416.

 

2023-03-07 16:52:01 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 34a3a460-b31f-4a62-99b7-17fa8cb5a39c. Error communicating with message broker"}
2023-03-07 17:38:05 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 0d55a12b-2e36-4c16-bf34-5b130e5748d5. Error communicating with message broker"}
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
2023-03-08 00:59:34 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 13f9eed0-3693-4df2-b601-4299af88fd0d. Error communicating with message broker"}
2023-03-08 01:17:59 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 8c84e08d-2513-4827-abfd-763d95d38358. Error communicating with message broker"}
2023-03-08 01:22:06 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 9664d53f-b6fb-4bbe-ae84-e91a0acff995. Error communicating with message broker"}
2023-03-08 01:25:41 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 33373143-c2ee-48fb-8900-c5e9259c76f8. Error communicating with message broker"}
2023-03-08 02:45:16 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: b808ec27-eb44-40b5-a2c2-188ea87e33de. Error communicating with message broker

 

-Timo-