It looks like your top field is on the same level as the entries below it. If that happens you are going to have issues.

It should look roughly like this:

So each of your evaluations that are inside a condition should be indented under that condition. If they are not indented one level deeper this won't happen. So in my example above lines 1, 2 and 6 all have to match, as well as at least any of 4 & 5. I also put the Template check at the end because all of the other evalulations can resolve without having to look up something in SQL - to determine the template name or field values it has to make a call to sql to retrieve the data. The user/path/name/document type are all things that the rule inheritetly knows when it checks your starting rules. Doing it this way makes evaluating faster, especially if you have lots of workflows as the rule checking stops the first time something doesn't match. 

One side note:

You really should consider putting in a  "user does not equal [workflow userID]". This is important to prevent accidental loops!!! Otherwise you could run into a situation where workflow has the capability of triggering itself if one of your rules is set to evaluate "on change" or "on move". This could be triggered by anything workflow does, such as set a field or rename a document.