Par andreasaulin

Elbert Dannenberg · ‎10-12-2024

Every month our customer sends an API call to General Ledger of approximately 13,500 lines. Previously this took approximately 45 minutes. Since last week they have received 500 reports. We have already divided the post into parts of 500 lines. Sometimes things go well now, but it takes upto 20 minutes per call, or we get error 500.

zunnu · ‎16-09-2024

You were right; they blocked all our IPs because we couldn’t refresh the token since their services were down..

Florian Haase · ‎09-09-2024

Hi Oskar, no, the problem was solved after we escalated it internally in Visma in the weekend. We could not wait until today since the whole integration platform stopped. I think somebody in the connect team knows exactly what happened, but I think it was due to a lot of token traffic from our side after the API got to live again. But we have to find out how we can quick enough answers when all is stopping due to such incidents also during a weekend. Florian

Sandra Anté · ‎07-02-2024

Thank you for reporting this issue. We are looking into it. Kind regards Sandra Anté

Magnus Johnsen · ‎17-01-2024

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4

Magnus Johnsen · ‎17-01-2024

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4

jnemo · ‎30-12-2023

Any update? 1st jan closing in

andreasaulin · ‎19-12-2023

The same again today ... 502 Bad Gateway

Yıldırım · ‎14-12-2023

Hello, according to our investigation this is related to a cache issue, that user which has been created for the Service type app on the fly is not immediately synced with the company that request has been made, therefore, usually a day helps to get this resolved upon server cache cycle. However, we're working to fix this, as the behaviour explained above is not feasible.

Yıldırım · ‎07-11-2023

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

andreasaulin · ‎30-10-2023

I've sent a few examples to developersupport now

JacobIpsen · ‎29-06-2023

i Got it working my local cashe where playing a trick on me Ctrl+Shift+R got it working. have u seem my question regarding findings in regards to warehouse and toWarehouse filtes ? it seems like toWarehouse filter only works if used WITH warehouse and not alone is this intended ?

KonsultVn · ‎31-03-2023

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?

Magnus Johnsen · ‎14-09-2022

Is this still happening? The development team is looking in to the issue.

adrianm · ‎15-06-2022

I still get this error almost every day.

Thomas Adrian - Consili · ‎13-06-2022

Hello Again My example may be wrong, I got it working if I send in the correct amount in the header when doing the PUT. it is still strange though that the payment is not closed, is it because of the balance i not 0, should the payment be set to closed ? how to do that?

Yıldırım · ‎06-04-2022

ℹ️ Inventory endpoint improvement for 8.91 has been disabled A fix is currently being worked on this issue.

Yıldırım · ‎24-01-2022

Hello, the issue experienced was related to the https://status.visma.com/incidents/xszmqh2wwbw6 which has been resolved in 09:59 CET 24.01.2022. If you encounter any problem concerning the same case, please contact us. Thanks.

Magnus Johnsen · ‎29-11-2021

Hi, Please follow this status page: https://status.visma.com/incidents/8b8nvbg7fqjm This is currently being investigated.

Magnus Johnsen · ‎17-11-2021

Hi, The solution for this is currently being tested and is as of now planned to be in the 8.75 release.

Magnus Johnsen · ‎20-09-2021

Today between 10:34 - 10:44 one of our nodes experienced a misconfiguration which led to routes of endpoints being not available on that node. This was quickly discovered and fixed. Sorry for any inconvenience.

Yıldırım · ‎20-09-2021

Hello, this has been planned to be fixed in Visma.net Financials API updates for version 8.66.0 (September 2021) Release plan may vary, therefore please subscribe & follow the thread and the "News" section. Thanks.

Magnus Johnsen · ‎15-09-2021

We have scaled out the application further, please let us know if you are still having issues. We are still investigating the cause for this.

Magnus Johnsen · ‎01-09-2021

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!

Yıldırım · ‎27-07-2021

Postmortem: https://status.visma.com/incidents/vghs93jnrqvd

Magnus Johnsen · ‎09-06-2021

Hi, We have asked the development team for another update on this case. We recommend that you lift this with your partner service as well.

Steinar Møller · ‎22-04-2021

Hi Magnus, An input, maybe this issue can be related to the update for Visma.net ERP around this time?

Magnus Johnsen · ‎22-12-2020

Thank you for confirming it works, please let us know if you have any other issues.

andreasaulin · ‎30-11-2020

No, it was fixed: https://status.visma.com/incidents/gh9ndhwrmqw5

Yıldırım · ‎25-11-2020

Update: The issue has been addressed. This was related to DNS, the issue has been occurred between our proxy servers and endpoint's environment. The problem should now be resolved. Postmortem will be provided at the status.visma.com We are sorry for the standstill this may have caused in your integrations. Please let us know whether you are still facing the problem.

Re: Increase in errors the last days

Sv: All integrations getting 403 / 401 response su...

Re: 403 Forbidden from /connect/token

Svar: Error 5102

Re: Bad Gateway messages when making calls to the ...

Re: Bad Gateway messages when making calls to the ...

Sv: Error: Branch '1 ' cannot be found in the ...

Re: 500 Error in every API call, Visma.NET service...

Re: POST Supplierinvoice using new authentication ...

Re: Instability from the API today and yesterday

Re: 5520

Sv: Timeouts from the InventoryTransfer endpoint

Re: Urgent - Connection to cache service failed

Re: GET inventory error, return empty

Svar: Processing Exception while reading ODP respo...

Re: Creating CustomerPayment using the API

Re: Attribute XXX not found

Re: API and api documentation unavailable

Re: Timeout from the API

Sv: Using "dunningLevel" parameter on customerInvo...

Re: Requested URI does not exist: /api/v1/SalesOrd...

Re: Inventory endpoint attachements

Re: System wide 502 errors and rejected logins

Re: Missing response posting SalesOrder

Re: 503 Service Temporarily Unavilable

Sv: /Inventory - pagination

Re: Updated inventory lastmodifydate

Re: Urgent - Placing orders suddenly receiving Err...

Re: Proxy error

Sv: Lots of 502 and connection errors yesterday an...

Noderīgas saites

Mūsu risinājumi

Seko mums