Docs not going to Workflow

[Jocelyn_Hannahs]

For reasons we have yet to discover, documents suddenly stopped automatically going into Workflow.  Our timer and scheduler services are running; our licenses are up to date; COLD and DIP processes are all running as they should.  But the docs just stop in the Committed or Awaiting to Commit queues.  Nothing has changed in configuration - this is our production environment and it has been a stable running environment for quite some time. 

This started happening during the workday.   We restarted the scheduler and that seemed to get things moving again, but only for a short while.   Over night the docs stopped going into Workflow again. 

Has anyone seen this behavior before?

[Paul_Flynn1]

Hi Jocelyn,

Have you reached the number of awaiting commited batches?  I would commit all uncommitied batches. These include other process such as scan queues e.t.c

Then see is the cold and dip process work.

[Paul_Flynn1]

Having just re-read this, I would just check that the documents are still assigned to the workflow, make sure the COLD and DIP configuration is correct . Are Cold and Dip configured so that documents  enter workflow during processing or once committed.?  if its commit, has the batch been committed?

If you import a file manually into OnBase does the document go into Workflow?   

[Jocelyn_Hannahs]

We have very few batches waiting to commit - we keep those pretty cleared out as a practice.  The docs are configured correctly as are the DIP and COLD processes, scan queues, etc.   We've even checked memory allocation on all of our servers and database tables.  Everything seems in order.   We have not tested the manual import of a file yet, as we've been manually executing workflow on large volumes of docs.   It's one thing to try at a later point.

[MichaelBertrand]

If your workflow is Core based, have you been doing IISRESETs for any reason? If the web server / application pool gets restarted any reason any process that uses the workflow will stop sending documents to workflow.  Unfortunately the OnBase services do not recover gracefully  from this sort of hang-up.

Typically we have a script that stops the various Hyland services, does the IISRESET and starts everything back up .