SpontaneousGrumbler wrote:

Today I'm getting "An error has occurred while searching: We could not complete your search due to a temporary problem. Please try again later." every time. At least some consistency has been achieved.

Yay? I've started work to speed it up by a pretty wide margin which should improve matters. It isn't going to change overnight though.

The error you are seeing is that the queue for new regex queries is full and it won't let you add another. I have a error messaging change in the pipeline that'll make that make more sense but I can't rush it through because if I did it'd go out untranslated.

The trouble with the regex queries is that there is only one line and some of them are fast because they have other filters but some are slow and the fast ones get behind the slow ones in line. That's why making them faster will help with the error messages.

The inconsistency is likely also caused by partial timeouts. In other words the search backend decides that it has spent long enough on the regex and just gives what it has so far. It won't have to do that if I'm able to speed up regexes though.

Related to, or possibly a duplicate of, T106685.