Customer Tags not being read correctly

[DatingDivas]

Working on setting up a flow for a subscription product. The goal is that a customer can join at any time and they will always get BOXA then at their renewal BOXB and so forth. We want the customer contact tagged with each box they have received so they never get the same one twice. 

We have started a flow were it looks for the subscription product, then checks the tags on the customer. It works for BOXA (or seems to) but when the renewal is placed it doesn't catch the BOXA tag on the customer and updates for BOXA instead of BOXB instead. 

Here is what we have... 

BOX A (BOX A wouldn't work with out it being 'non of the orders' & 'does not include'.)

Then if they have the BOXA tag it should go to this condition for BOXB (and BOX B actions)but it doesn't... it continues the BOXA actions

Again we want it checking customer tags for the previous tag to know what part of the flow to action. 

Any help?

[Steve_L]

I think it's the double negative in the BOXA condition that's causing the issue. Let's say the customer has the tag for BOXA. If you check that none of the tags do not include BOXA, and the customer has BOXA then it will return true. The reason it works on the first pass is because of how empty lists are treated in our underlying language.

I think the logic that you need is to check that none of the customer tags include (or are equal to) the tag.