Better errors when something fails on search

[mauricioszabo]

Before:

After:

[confused-Techie]

@mauricioszabo just wanted to let you know that the backend codebase should already have a fix applied for returning { message: "Not Found" } instead of the proper []. The fix needs to just go live

I'm not sure if we want to still merge this because it very well could be helpful, especially to identify if theres any other bugs in the returns. Just wanted to let you know

[mauricioszabo]

I think it's a good idea to merge, because if the server 500 or times out or, for some reason, our DNS gets outdated, or blocked, we can see what the server is running

[confused-Techie]

After dicussing this with @mauricioszabo looks like this will still be a good feature to have even with the backend returning properly for the item that initially brought about this change.