Unindexed batches are getting committed

[Ted_Cannelongo]

We're using the OnBase thick client version 12.0.0.540 to index batches in our production environment.  We have been seeing rare occasions where a batch will be committed, yet the user did not index any of the documents in the batch.  I don't show any exceptions in obClnt32.RPT around the time that it appears the back moved to Committed.  Here's the batch summary:

---------------------------------------------------------------------------------------------------- 
Batch Summary Report : Batch 647276 (Mail-Bills-9-30-14) Page 1 
---------------------------------------------------------------------------------------------------- 
Scan queue 135 (Received Mail) 
Current batch status: Committed 
-# Indexed documents = 0 # Unindexed documents = 69 

Batch History 
--------------------------------------- 

02:23:52 PM Tue 09-30-2014 - Batch create 
02:23:52 PM Tue 09-30-2014 - Awaiting Image Processing 
02:35:49 PM Tue 09-30-2014 - Scan/Sweep Operation Completed 
02:35:49 PM Tue 09-30-2014 - Automatic batch image processing 
02:35:49 PM Tue 09-30-2014 - Perform batch image processing 
02:36:17 PM Tue 09-30-2014 - Awaiting Index 
09:56:00 AM Thu 10-02-2014 - Awaiting Post-Index Scan Queue Sorting 
09:59:28 AM Thu 10-02-2014 - Performed automatic scan queue batch document sorting (post-index) 
09:59:28 AM Thu 10-02-2014 - Awaiting Commit 
09:59:28 AM Thu 10-02-2014 - Automatic commit 
09:59:32 AM Thu 10-02-2014 - Manual commit 
09:59:33 AM Thu 10-02-2014 - Incomplete Commit 
09:59:33 AM Thu 10-02-2014 - Committed

Has anyone else encountered this?  I cannot seem to find a way to reproduce it.  In this particular case, they need to later create an outbound fax from the documents in the batch, so they happened to notice that it was missing, but I worry about other situations where we could be missing deadlines as documents are never indexed.

[Steve_Reed · Accepted solution]

Hi Ted,

We had an issue related to the problem that you are experiencing and we've since addressed it in version 12.  I'd suggest you contact your support representative and refer to SCR 167325 to get an updated build of the software.

[Bob_McIntyre]

We are experiencing the same recently.

We added two new queues to our process but that is in Pre-Indexing stage. Yesterday (10-13-14) and Today (10-14-14) we have had some Batches move from Awaiting Re-Index to Awaiting Commit whithout being Re-Indexed.

We are using 11.0.1.560

Is there a SCR for our version?

Thanks for any help

Bob McIntyre

Charleston County RMC