Workflow Timer only executes one document in the queue and stops

[Jim_Wysocki]

We have a timer that is configured to run for All document types at 4:00am, every day of the week.  Unfortunately it only processes one document in the queue and stops.   The First Document Only checkbox is not checked.

We are using the Timer Service to execute our timers, and other timers that are configured to run every 5 minutes work fine, meaning they process all the documents in the queue.  If I run this particular timer from the Timer Service Administrator, it also just processes one document instead of all documents in the queue.  However if I execute the timer manually from my workstation using the Classic user interface of my client, it will process all the documents in the queue, not just the first one.  If I change my workstation to the Default (core-based) interface, it will only process one document when running just like the Timer Service.

Any ideas as to why this is happening?  I'd prefer not to manually execute the timer every day.

Thanks

[Jim_Wysocki]

Just to keep things simple, in my test scenario, I set up the documents so that they wouldn't get added to the other life cycle (meaning the Date of Service was within the last 60 days).  Looking at the workflow trace, the rules are evaluated as expected, it just stops after the first document for some reason.

[Dave_Romel]

Just fishing here, but have you restarted Timer Service on the server recently?

[Jim_Wysocki]

I did end up calling support and after about an hour, we figured out that we had to un-check the Auto-Feed Document option on the standard tab for the queue configuration.  Apparently this issue has been fixed in version 12, but we're still on version 11.

[Paul_Lloyd]

Jim, thanks for the follow-up post. Auto-feed was something I wouldn't have thought of. I'm glad you were able to resolve it.