@ Nicholas - Good ideas. I tried to test this morning and get you the information you asked for but for some miraculous reason it started working. I didn't change anything other than rebooting my computer when I left work for the night. I have no explanation for it. I have the same stage, the same filter, the same items in my queue.
To give you a specific answer to the "what is it pulling that it shouldn't", my app names aren't what I'm using in my sample, but I was filtering for
And getting items with this tag
MRDC_Review_2021_02_23_12.41.xlsm_Row 23;Second Review;CM Complete;Nautilus Complete
no reference to DNA in the tag of the item that returned, and I went through all the characters - there is no "DNA" anywhere, although that "nd" in second did worry me for a bit. The only variable within the tag is the date/timestamp after the file name (first portion of the tag), and the Complete/Exception after each app name, so there's no other way for the characters "dna" to end up in the tag unless it's in reference to my application being worked.
@ Harpreet - my understanding is that all tag filters are AND which is why I didn't do something like "Word Complete or Word Exception". I went back to the "Advanced Work Queues Guide" from Blue Prism to double check that I didn't miss something when this wasn't working and it states that all tag filters are AND. Also, your method won't work because the purpose of the stage is to check that there are no items in the queue where all three applications have been worked but it's still not showing as "completed". I need ONLY items where all three apps are listed in the tag. Any other information is irrelevant to me. I can't pull them, check the tags, and then defer for X time, either, because my process runs in such a way as that might cause items to either be missed or get me into an infinite loop of pulling, checking, deferring, pulling again. I do appreciate the idea, though! in a different situation it might work, just not this one.
Long reply to say, for some gremlin reason it works now. I'll run about 1000 tests to make sure that it keeps working and update again with Nicholas' requested information if it breaks again. Thanks for the help!