BIX fails because work object is locked
BIX appears to be failing when the case is locked. We run BIX during off peak hours but it will regularly encounter work items that are locked by a user or agent process. When this happens the work object is not BIX'd because BIX can't get the lock. Is this the correct behavior? Why does BIX need a lock? I'm expecting BIX to be a read only process. If the current record is locked and dirty that's ok. Any committed changes will be picked up on the next BIX run.
***Edited by Moderator Marissa to update platform capability tags****
Swedbank AB
SE
Hello John,
It could be because you've configured the BIX with "-f" parameter, which Forces the extract to stop at the first error that it encounters.
Kindly refer BIX logging and BIX error handling to know more.
Let us know if this helps!
Thank you,
Pawan
Computershare
US
John posted this question for me. However, the issue is not that BIX fails (it does not), but that it will skip the work object (case) that is locked. It continues on to BIX other cases. There is no error thrown by BIX. It simply skips cases and moves on.