Lots of timeouts from the API now

[JoLu]

Hi,

We are still seeing problems with performance and timeouts in the API, fetching customer invoices can take several minutes for one page of 100 invoices (if it even can be fetched before the timeout of 20 minutes that we are using). Could you please check if there are any issues with the API.

Best regards

Johan

[Yıldırım]

Hello Johan,

is the performance better now or are you still experiencing timeouts more than usual ? 

[JoLu]

Hi,

We still get timeouts now and then even for requests that only fetches updated entities and the company 2730*** could still not be fetched at all.

[Yıldırım]

Further instructions regarding company "2730***" has been sent via email. 

[Yıldırım]

Hello Johan, 

Are the companies you experience a slow-down the same that you've shared earlier ?   (185***, 208*** and 367***)  

[JoLu]

Hi,

The biggest issue is for a company with Id 273**** which we can't fetch data for due to timeouts but the issue exists for several customers but that is manageable at the moment since for them we only have to get the changed data as of now. The performance is not always bad, it varies very much and sometimes a call may take 17 seconds but the next time it is tried it won't return anything before the 20 minute timeout.

[Yıldırım]

I see, could you please send the full company ID (273***)  ? It does not seem between the ones that you've sent yesterday. Just to confirm, please also send your full request URL. 

Thanks.

[JoLu]

I have sent an e-mail with some details!

[Yıldırım]

Application Response-Time in the Financials ERP has been increased "11:48 CET" which has been neutralized at "12:34 CET" today. Currently, performance monitoring does not show any performance degradation. 

Regarding the fluctuation that you have been experiencing, this is related to the multitenant environment and shared limited resources between other Integrations and companies, therefore, this may happen in certain high load periods. This has been marked by the team as normal within the acceptance criteria If it's for a short period of time and can be mitigated with 5-10 retries.

However, we're going to inform the infrastructure team about this for the company-ID you've shared. We'll keep you updated on the latest news from the team.

[JoLu]

We have tried to fetch data for that specific company since 2021-12-06 without success.

[Yıldırım]

---

@JoLu wrote:

We have tried to fetch data for that specific company since 2021-12-06 without success.

---

---

@JoLu wrote: <Ticket:#2093027>

As per request in the forum here is the companyId: 273*** and one of the calls we make is

https://integration.visma.net/API//controller/api/v1/customerinvoice?financialPeriod=202101&expandAp...

which at the moment takes about 15 seconds to complete but when tested previously this morning it timed out after 20 minutes and we have tried to fetch data for this company the last couple of days and it fails every time due to timeouts, mostly in the supplierinvoice or customerinvoice enpoints.

---

• What is the total data-size of the customerInvoice / SupplierInvoice based on applied filters that you'd like to fetch ? <financialPeriod=202101&expandApplications=true&page=1&pageSize=100>
• How many "PageNumber" in total you need to divide the data into ?  

E.g. can be found in returned EOF JSON

 

• Is the request always times out on a specific pageNumber ? Since you mentioned that &page=1&pageSize=100 "took 15 seconds to complete" in one of your recent tries. 

[JoLu]

When testing the calls I saw that there where about 2300 customer invoices for the period 202101 and it seemed that it is more or less the same for other periods as well, so that would mean about 23 pages for that period, and we are trying to get data for three years in total.

For supplier invoices there are about 14000 invoices and we are currently trying to get them using a page size of 500.

The timeout can happen on any page, this morning I tried the same call and that timed out but now when testing it takes somewhere between 15 and 30 seconds for customer invoices.

[Yıldırım]

In this case, please elaborate what you define as "without success". 

---

@JoLu wrote:

We have tried to fetch data for that specific company since 2021-12-06 without success.

Have you managed to get all pageNumber<1 to 23> with PageSize<100> for the customer invoices of the period "202121"  even though some pageNumbers inquiry time-outs ? 

If some  pageNumbers time-out, you should specifically retry those failed "PageNumbers" until you got the full data and store them instead of re-querying from the beginning. 

---

[JoLu]

Without success means that we haven't been able to get a complete set of data for three years for the company, we fetch financial years, accounts, account balances, cost centers, projects, general ledger data, customer and supplier invoices and it has failed in one or more of these areas in every try we have made. 

We do retries for every request (page) up to five times with an increasing back-of time until we get the data or the request times out, which is set to 20 minutes per request, and then we consider it to have failed.

[Yıldırım]

Hello Johan, 

thanks for the details.

The company, 2730*** where API transactions have been specifically experiencing performance issues is under infrastructure team's watch, and they're currently working on some node level improvements.