In this case the initiator is a specific person...so I  route the document back to that person's folder, however, because the Workflow has already started, it doesn't do anything when it goes back to that persons folder even when the criteria meets the wait condition already set forth for that Route Entry To User.  Below is my workflow...the starting rule is "Entry Changes" and Path=Incoming Batch and Field= Yes or No.  Notice the section I've highlighted is where I'm having issues...if the document needs changes, it gets routed to  John R. "Batches Needs Changes" folder, once he makes the changes he changes the status of field "Is the document codable" to "Yes" and it goes back to Afyia folder to review again, which in turn starts the process again, however, when it get's there...even when the document meets the Wait Conditions...nothing happens.  It's a potential cycle that can go round a round a few times before the document is completed and the Workflow would be completed.  

I'm not quite seeing what it is that you are attempting to do. It seems like you have a starting rule on the "Batch Needs Changes" folder? If that's true, you should remove it, because the wait condition should do that for you.

The real issue is why your wait condition isn't working as you expect. Do a search for one of the workflows that's stalled at the Route Entry activity and open up it's instance information. There should be a "Condition" tab that will let you see how the wait condition criteria are being processed.

Devin,

No, my starting rule is not on the "Batch Needs Changes" folder, but what the customer does is they do a mass import of documents into an "Incoming Batches" Folder.  From there...they go through and identify the documents.  My starting rule is based upon a "Change Entry" in the Incoming Batches folder and the field "Is it Codable" = Yes or No.  From there, it kicks off the workflow and if it's Non-Codable, it goes directly to the Customer Care folder.   If it IS Codable, it goes to Afyia for review.  From her, she can either agree that it's Codable and route it to Coding, Determine it's Non-Codable and route it to Customer Care, or she may determine it Needs Changes and route it back to John R. (who did the initial import).  Once it goes back to John R., he needs to look at it again, and from there can determine again if it's Codable or Non-Codable (which would then run through the workflow cycle again).  I can get it to work if I simply create a second starting rule for Entry Change Path= John R.\Batches Need Changes\ and field Is it Codable= Yes or No, but then I loose all my tracking information from the Business Process because it starts over.