Customer invoices not being released

[Anonymous]

We are creating and releasing invoices through the api in large batches, but some of the invoices are not being released even though the api returns no error. The procedure for each invoice is:

- Save the invoice

- Create an attachment

- Release the invoice

The api returns no errors for any of these calls, but a large number of invoices still are not released 12h later. The invoices that hasn't been released can be relased manually in Visma.net Financials. 

[Anonymous]

Also, I don't know if this is just a coincidence, but we started seing this behaviour with failed release the last few days, after we also started creating attachments for all the invoices. So we:

- Save the invoice

- Create the attachment for the invoice (same attachment file for all invoices)

- Release the invoice

All the steps succeed without errors, but som invoices never get released.

Edit: Also, we handle invoices in parallell. We always perform the steps above in the order described for the same invoice, but we send calls for different invoices in parallel. This shouldn't be a problem, right? We comply to the rate limits att all time, maximum calls/h, max concurrent calls and so on, and we never get any error codes of any kind.

[Anonymous]

We currently have no retry logic for invoices that get no error from the api, and we really shouldn't need that I guess. If the job is queued in Visma without errors we expect the job to get executed unless there is something wrong with the invoice (but in that case we would expect the api to not queue the job and not return 200).

Since these "failed" invoices can be released without any problem later on in both the api and the UI we expect them to actually be released a some point in time, if we get code 200.

[Magnus Johnsen]

Hi,

As all release operations are implemented at the moment, the response is always 200 when it has received the request to start the job. 

The issue that some jobs are not completed are the same happens the same way as it does in the UI.

With the long running operations we are presenting in the webinar, you will be able to keep track of the status of these jobs.

For now, this is not possible. 

[Magnus Johnsen]

Hi,

The release operation returns a 200 status code when the job has been started and does not return an error unless it failed to queue the job. As of right now, there is no way of seeing if this job has failed for any reason.

Since you mention that you release them in large batches, the issue might just be that the server is not able to process the at the given time, have you tried releasing them via the API again or only via the UI?

We have a case in the backlog concerning these long running operations, you might be interested in joining the up coming webinar where we will talk about this among other things: 

Announcement : Webinar - Visma.net Financials ERP API / 14-12-2021 

[Anonymous]

Do you have any idea why the release operations fail in Visma? Is there anything we can do on our end to prevent this? The night between monday and tuesday we exported 18000 invoices to the api, and 8000 of them never got released in Visma even though the release operation got a 200 status code on all of them. A 45% fail rate in Visma is not that great and there must be a way to investigate why this happen and what we can do to avoid it.

[Magnus Johnsen]

Could you please send us the companyID as well as some examples of invoices that were not released to developersupport@visma.com and we'll see if we can see any reasons in the logs.

Thank you. 

[Anonymous]

I've sent an email to developersupport. Thanks for your help!