@VLAZ That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
what happened 11 days ago? my automated flags all failed. I am used to get 1 or two flags per month, but 11 days ago i had a hundred or more failed attempts of flagging
@Dugnom yes; there was a large spam wave; see the "Flagging results daily, last month" chart at metasmoke.erwaysoftware.com where there were 102686 total flag failures
(along with a local maximum of successful flags, it should be said)
@Dugnom As Jeff pointed out - big spamwave. The declined flags were partly because SD had a hard time coping with such volume. It kept trying to use votes from users who had already ran out, for example. Which exacerbated the failure count.
@VLAZ That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 844-556-7122 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 844-556-7122. Append -force to the command word(s) if you really want to add the pattern you provided.
