Reoccurring error messages from the API even if there are no issues

[JoLu]

We get error messages from the API almost every day for our integration, on all our connected customers and on different endpoints, sometimes several times each day. Most of the times there are no real issues and even if the error messages indicates problems with tokens etc it works if we retry the requests after a while without doing any new authentication etc. Examples of the errors we get from the API are:

- Exception while trying to validate user context in ODP based on token.

- Invalid parameter exception: companyInContext

 Is these error messages something that we can ignore or may there be situations where they actually indicates real errors? We are using a retry policy for our requests so that we retry erroneous request up to five time with an increasingly longer wait period between the requests before we stop trying and signals an error but even with these retries if fails. The last time we experienced these issues was 2021-12-08 00:35 (UTC).

Best regards

Johan

[Yıldırım]

Hello, 

@JoLu This seems to be related to the access to Financials ERP Company. Since when you are facing this issue, and when was the last time you've received ? Could you please share your API Client ID, Issue occurred CompanyID and some example operations with ipp-request-id , error timestamps if possible ? <developersupport@visma.com>

@Anonymous 
We've experienced some issues during the midnight that might've caused the mentioned issues, due to <https://status.visma.com/incidents/pbl1mmvcyq5f>

timeouts can be expected for big-data size transactions but to be certain could you please share some details from your request such as API Client ID, CompanyID, error timestamps, your request URL ? <developersupport@visma.com>

So that we can investigate the aforementioned cases in detail.

Thanks.

[JoLu]

Hi,

We have experienced these kind of errors and others as well since we started to use the API but they seem to happen more frequent nowadays. As I wrote in the initial post the last time we experienced these issues was 2021-12-08 00:35 (UTC). I have sent examples of the latest errors to developersupport@visma.com.

Best regards

Johan

[Yıldırım]

Thank you for the information you've provided.

The error message  <companyInContext","ExceptionFaultCode":"12002",> indicates that your token (generated from visma user) does not have access to the desired company. 

Please make sure that,

*user has been granted Financials Administrator & Financials User roles on the specified companies. 
*Request Hedaers: "ipp-company-id" value is correct, and it's visible when you make GET:Context<https://integration.visma.net/API/resources/v1/context> request with authenticated user's token.

B) And the other error message, <Exception while trying to validate user context in ODP based on token> might be related to the Financials ERP company licences that user numbers / services may have been exceeded the number of the licence defined (allowed)  in the company. 

Please check the Financials licences in use.

*See the article for reviewing the aforementioned point A & B regarding the error messages you're receiving with the used ipp-company-id's: Connecting your Visma.Net Financials company to the API

[JoLu]

Hi,

Thank you for your answer. Since the last errors happened almost at the same time for all of our customers I don't think there are any issues with either the company access or the licenses and the integration starts to work again after a while without any user intervention. Could you please check on your side again why these errors occurs and if they are safe to ignore in most cases?

Best regards

Johan

[Yıldırım]

Hello Johan, 

"Since the last errors happened almost at the same time for all of our customers I don't think there are any issues with either the company access or the licenses and the integration starts to work again after a while without any user intervention. Could you please check on your side again why these errors occurs and if they are safe to ignore in most cases? "

We've not seen anything abnormal with those companies

• (18545**)
•  (20824**)
•  (36721**)

The reason that you might have received the mentioned error with all the companies on December 8th is due to the scheduled maintenance <https://status.visma.com/incidents/pbl1mmvcyq5f> since Visma.net Financials & Logistics, Payroll & HRM services were not available during the window so that they cannot be accessed. 

Please let us know if you receive the same error again, sharing information about the instance such as 
-CompanyID
- Authenticated User during Token Generation <xxx@xxx.com>
-Error Message 

Apart from the times that Services are unavailable and although you've mentioned that "the integration starts to work again after a while without any user intervention"

It's still worth checking the "licence in use / allowed numbers" in the issue occurred companies.

Connecting your Visma.Net Financials company to the API

This is possible that if a new user granted access to those companies where its licence exceeded and then revoked the access so that it was continuing to working as expected.

Thanks. 

[Anonymous]

I can confirm that we also get the above errors in large numbers. Last night we started exporting 70000 invoices to Visma through the API, and between 01:00 and 02:45 tonight almost all of the export attempts during that time failed due to the above errors.

After 02:45 things have gotten better but we still get random timeouts.