We are seeing some exceptions for some of the work objects when Service Level Rules are getting executed. This results in work objects getting moved to Broken-Process queue. The errors we are seeing are - "** caught exception during autocommit check" or "The assignment for this queue item has a problem". Any inputs or suggestions on the possible root cause and how this can be resolved would be appreciated.
Check if the related flows where the assignment is waiting were changed (assignments were moved) in the recent times and the old assignments were breaking due to the flow changes? We faced a similar issue.
ResumeFlow activity has a commit included as one of the steps and it releases the lock on the workobject and when the QueueManager (SLA) tries to commit the workobject, it doesn't have the lock and commit fails.
In order to get rid of this problem, ResumeFlow activity should be included in a wrapper activity and a parameter CalledFromServiceLevl has to be set to true. This parameter is already provided by the ResumeFlow activity. The Wrapper activity should be used as an escalation activity instead of ResumeFlow directly.
We aren't seeing Auto Commit errors now after writing a wrapper activity for Resume-Flow, but still we see some items in Broken-Queue with a message "The assignment for this queue item has a problem". Any suggestions?