Hi folks, long time no see!
Since a couple of months, we get this exception on almost all of our processes:
ERROR: Internal : Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Operation cancelled by user.
Obviously, the process then terminates. However, most runs complete normally, but we have a few of these exceptions on various processes almost every day. The process is then rerun and ends without issues.
The exception above is exclusively thrown by any action withing the native BP object 'Work Queues'. We found it can be 'Get Next Item', 'Set Status', 'Marks as Exception', 'Mark Competed', or any other action within this object. We have not seen this exception on any other native BP object or indeed on our own local objects.
I found that a similar issue has been reported in this community before, and a link to the solution/workaround was provided. Unfortunately, the provided links are no longer valid.
When checking the server (VDI) we run our processes on, it was found that very little free disk space was available. Subsequently, a cleanup operation was started and now there's enough free disk space. This did however not solve the issue.
It was also suggested to avoid WorkQ Item collection data containing many columns and/or many rows. We don't have any of that.
As a final solution, I was told to add a resume-recover-loop construct in order to handle exceptions on all BP object actions that are known to throw the exception. Obviously, we could try this but I think this will lead to more problems; the only thing to do if it fails repeatedly is to terminate - which is what we have today. Also, I feel it is a problem with either the network or with the BP object not the process - with my money of the BP object.
Oh, we're at BP 6.10.5 if that matters.
Any thoughts, ideas, tips, suggestions, workarounds or solutions? Anyone?
Happy coding!
-------------------
Paul
Sweden
