@ProcessedMeat Does that throw a touch of suspicion on meta.stackexchange.com/a/370149, which was reported in here and given an FP after a mod deleted/undeleted it?
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in bodyThe regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command if you really want to add this pattern.
@cigien 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 if you really want to add this pattern.
> "... There are an unusual number of requests coming from this IP address.</p> <p>To protect our users, we can't process any more requests from this IP address right now.</p> <p>We'll restore access as quickly as possible, so try again soon. ..."
@Rob Yes, there's an issue there, which has been the case since we started autoflagging. I believe I know what it is and how to fix it. I have partial code.
@ThomasWard @Undo @ArtOfCode It's not a new issue. The problem has been around for forever. You're welcome to work on it. If so, tell me and I'll stop working on it. But, it's a general overall issue with how MS handles SE API accesses. It's in MS, not in the Lambda.
It's deleted now, but before it looked like either 'exceeded quota' or 'rate limiting' based error - and not already deleted, which doesn't reply with a full header of red text.
