As I said in MBS-5046, "It seems that if we can't eliminate the 502s entirely, it should at least catch them and render the edit search and a message saying the search took too long to run, so the user can try narrowing down their search."

That's what we did pre-NGS, but now we just show a useless nginx error page and the only way to change your search is to start all over again.