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?

[#2]

Just a thought: You may see that behavior after a reset of the app server causes the client on the processing workstation to lose connection with the appserver.

[Jocelyn_Hannahs]

In our production environment we are very, very careful not to do any iisresets or restarts on the app server until off hours - unless there is a critical production issue that requires it (in which case we have all users get off the system and stop all processes before the reset is done).   There were no iisresets done yesterday during business hours - at least none that we know of!

[MichaelBertrand]

I would suggest activating (if need be) Applicaiton Pool Recycling logging, just to be sure that there is not some hiddent process or condition that is causing the resets. Look at the history of a document that did not go to workflow. If the workflow history says something like Invalid Queue it could be a further indicator that it is a reset. 

You can put a Diagnostics Console on it and log until the issue happens. Yes, it will be a large log, but may get an error message out of it. 

[D_Aunn_Bednarz]

We had this happen when someone remotely logged into the Server running the Core Based Workflow, logged into the OnBase Client on that server with their userid (instead of the admin userid).  Their userid was setup to use Classic Workflow instead of Core based Workflow.  This caused the documents to have the "Invalid Queue" error in the Workflow History of the documents.  To fix this issue, we just logged into the OnBase client on that server - using the admin userid, and made sure the Workflow was set to Core based.

[Linda_Hankemeie]

We've had this issue happen as well.  We found that when we restart services they need to be done in a certain order.   Workflow timers need to be restarted before the scheduler service.  We have our services restart every am and had to have the order set correctly.  

We were just discussing this issue and how to identify documents that are not going into workflow.  The suggested solution was to have a keyword in the DIP file that is KW:  Workflow and set to no.  The first action in workflow would be to change to Yes -- then we can do search for docments that are still No in that particular keyword.