Search for Literal String does not work properly

We have a large group of errors where the Message = "TypeError: e is undefined". Since I cannot put colons in the literal string to search for I tried searching for "e is undefined" What I got back was a result set that seems more like the individual tokens were ORed. As a result I'm incorrectly getting results where messages = "TypeError: undefined is not an object"

All the following yield the same incorrect result set

/search?q="e+is+undefined" /search?q=e+is+undefined /search?q="e%20is%20undefined" /search?q=e%20is%20undefined

This one doesn't seem to narrow it down properly either. The result set is smaller but there are still values returned that aren't what I literally specified

/search?q=message%3A"e+is+undefined"

---