Hi ,

Is there way to identify the cause of  lock failure with OOTB Job schedulers .

all nodes health in cluster looks good .

2025-02-21 09:27:56,015 [OBSCHEDULER_THREAD_9] [  STANDARD] [                    ] [                    ] (         JobSchedulerLifecycle) ERROR    - [PersistentJobExecutionFactory] Job[pyAlertJobForMaxErrorRecordsOfLSETable] execution lock has failed.  com.pega.pegarules.pub.database.LockGoneException: Database-LockFailure-LockLost    PYALERTJOBFORMAXERRORRECORDSOFLSETABLE      at com.pega.pegarules.data.internal.lock.LockManagerImpl.checkRequiredLocks(LockManagerImpl.java:1182) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.checkRequiredLocks(UpdateProcessor.java:929) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:290) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:108) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.store.DataStoreManager.doInTransaction(DataStoreManager.java:273) ~[prprivate-data.jar:?]      

          2025-02-21 09:27:55,013 [BSCHEDULER_THREAD_10] [  STANDARD] [                    ] [                    ] (         JobSchedulerLifecycle) ERROR    - [PersistentJobExecutionFactory] Job[pzResetExpiredLogCategories] execution lock has failed.  com.pega.pegarules.pub.database.LockGoneException: Database-LockFailure-LockLost    PZRESETEXPIREDLOGCATEGORIES      at com.pega.pegarules.data.internal.lock.LockManagerImpl.checkRequiredLocks(LockManagerImpl.java:1182) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.checkRequiredLocks(UpdateProcessor.java:929) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:290) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:108) ~[prprivate-data.jar:?]         

2025-02-21 09:27:54,012 [OBSCHEDULER_THREAD_1] [  STANDARD] [                    ] [                    ] (         JobSchedulerLifecycle) ERROR    - [PersistentJobExecutionFactory] Job[pyManageIncrementalIndexer] execution lock has failed.  com.pega.pegarules.pub.database.LockGoneException: Database-LockFailure-LockLost    PYMANAGEINCREMENTALINDEXER      at com.pega.pegarules.data.internal.lock.LockManagerImpl.checkRequiredLocks(LockManagerImpl.java:1182) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.checkRequiredLocks(UpdateProcessor.java:929) ~[prprivate-data.jar:?]      at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:290) ~[prprivate-data.jar:?]      

Not sure if below bug is related to the above exceptions but it's resolved in 24.1 

    ​​​​​