Hi Jacob,Thank you for your reply. I totally agree that there are
multiple ways to create the Regex, and we have tried multiple ones, from
a very tight one as you suggested to the simpler one I included in the
posted question. The result is the same. The point here is different.
The Regex was tested, using the Classification Rules testing tool, and
with an independent tool. In both cases the Regex matches the cases in
question. This doesn't seem to be a Regex issue.
Hi Khurshid,Thank you for pitching in. There is actually to time
limitation for the rule in question, and it is not because the entries
are too old. Even more recent entries are impacted. It is just very odd.
I don't think I am the only one seeing this. I posted this same question
on the #measure Slack channel and some participants confirmed they have
seen this behaviour, however they have not idea why does this happen.
I have a similar issue, with a classification rule applied to product
values (details included here:
We have double checked all the recommendations presented here and
everything seems to be fine (there is even no chance of other rule
conflicting). Do you have any idea on what may be causing this? Is this
perhaps a known bug?
We identified a issue with a Classification Rule for one of our clients.
It is an odd case we have not found any documentation about. While
applying classification rule on the product values:1. There is a
classification rule created using a Regex, that sets one constant value
as a result. Here is the expression:
.*Promo.*Streaming\s-\s[1-4]mo.*|MobileOAC:Promo - Premier Streaming -
6mo - 30.00 - 1moFO|.*Trial.*Streaming\s-\s[1-4]mo.* 2. When running a
test on the set of values, they are all clas...