Virtual Service Using Cookie Persistence and Multiple Pools

I have a virtual service using cookie persistence and multiple pools. A policy examines the URI such that: if the path is /x send the traffic to pool "x" if the path is /y send the traffic to pool "y"

Now both persistence cookies are used by the client. During normal operation, after the initial requests, it is possible for the user to send requests to path "/x" or "/y".

My question is this... When the following requests from the client hit the LTM

Does the the logic first process the examination of the path , then check the cookie persistence for that specific pool?

 OR

Does the logic take a look at the two persistence cookies first before examining the path, thereby possibly sending the traffic to the wrong pool?

As a side note, the virtual service is using the One Connect profile.