We regularly get a lot of jobs stuck at 100% when you run the getoperarions query to connect server, should you have jobs stuck at 100? Is this normal
This can occur when the result of the Output Creation operation has not been retrieved yet. That should not occur with Workflow Tasks, unless there was some error during the process.
Or could it be that you are triggering these operations via the REST API directly? In which case, you could simply issue a Get Result of Operation command, which should then mark the entire output creation operation as completed.
Hi,
No we don’t call anything via the APi, but we do often get the below errors so guess it those jobs
Error Message : W3001 : Error while executing plugin: HTTP/1.1 500 Internal Server Error - An unspecified error occurred which was caused by LoggedApplicationException: There was an error running the output creation process caused by ApplicationException: null (SRV000042) (SRV000001) | 1: ERROR HERE | Create Output: W1603 : Plugin failed - 08:15:20 (elapsed time: 00:00:01.758) |
Error Message : W3001 : Error while executing plugin: {“error”:{“status”:500,“message”:“Deadlock found when trying to get lock; try restarting transaction”,“parameter”:“”}} | 1: ERROR HERE | Create Print Content: W1603 : Plugin failed - 15:47:32 (elapsed time: 00:00:02.010) |
Do you have more than one process that uses Retrieve Items plugin? Or maybe a process that is self-replicated?
Normally that error occurs in a database when multiple queries are trying to access the same record.
Yes we have lots of jobs which use retrieve items (50+) and also 1 main self replicating tasks which applies production marks etc for jobs which allows 5 jobs to run at once
That looks to be the source of your problem. Could be that one process is creating a record while another one is trying to access it.
You might want to review your logic taking into account the creation and access request of records in Connect database.