Document Revision record is currently locked - Background Jobs failing

Hi,

It’s hard to know without knowing exactly what the background is doing. Also, do you have any custom events in this area?

I recommend contacting our support who should know about your solution, and/or any consultant that has helped you set these things up.

By the way, there are quite many jobs running at the same time there. What starts these jobs?

To answer your question about “looking”. If you mean to view the document, that operation is creating a history record. Perhaps, if someone happens to view the document at the exact same time the background job is running, a locking issue can happen.

/Mathias

If you look at the field “Function” in the background job and it says “INVOICE_IMPORT_UTIL_API.Release_Document__” this is solved in bug 156683.

I’m not 100% sure about the problem but if your batch queue “2” has more than 1 process you might avoid this by directing the method “INVOICE_IMPORT_UTIL_API.Release_Document__” to a batch queue with 1 process.

Thank you Mathias. Not sure if there are any custom events here. But it seems like the job is trying to release the documents via Invoice_Import_Util_API.

Tomas Ruderfelt wrote:

If you look at the field “Function” in the background job and it says “INVOICE_IMPORT_UTIL_API.Release_Document__” this is solved in bug 156683.

 

I’m not 100% sure about the problem but if your batch queue “2” has more than 1 process you might avoid this by directing the method “INVOICE_IMPORT_UTIL_API.Release_Document__” to a batch queue with 1 process.

 

Thank you Tomas. I have checked the function field and it indeed says Invoice_Import_Util_API.Release_Document__ . Where can we find out more about the bug which you have mentioned and how can we know how many versions we are behind that fix?

Our queue “2” has many jobs. And all of those jobs have 1 process.

Thank you Tomas!