Can't search "your books"

There is a problem searching. Message says:
"Some sort of error just happened. The error was logged and Tim has been alerted. If problems persist, email timspaldingAT SIGNlibrarything.com

In most cases, the problem can be fixed by using this link.

The reported error was:

Problem with the concurrent query manager in the LibraryThing Bureau of Garbage Collections.
We have an entire room of trained monkeys working to solve the problem.."

I had that too yesterday. On a specific query; a combination of a tag and collection search. Any other query was fine. Went away after a little while (around an hour maybe).

Still having that problem - has not let up and its been several days now. Cannot search my books. Just using book titles and get same error message. Librarything troubleshooters - can you help?

>3 Jahsena: Please give a concrete example. "book titles" is not concrete and bugs are elusive creatures. So if the search fails for all other book titles than "Software Psychology" that is sure to be the book title, the troubleshooters will try.

Bug reports are the only literary genre where you'll get praise for assuming that the audience don't know anything about anything and must have everything explained :-)

>4 bnielsen: Interesting. I just got this error searching @Jahsena's catalog for Thou shalt innovate. I did not, however, get it for the title A moment in time.

(Which rather proves your point about the need to be hyper-specific in bug reports, even when the pattern appears obvious.)

>5 hipdeep: Curie and Joliot (famous physicists) had made an important nuclear experiment, reported on it in a paper, and went on holiday. Returning to the scorn of colleagues who couldn't replicate the experiment. And then finding that they (i.e. Curie and Joliot) also couldn't. It turned out that the difference between working and not-working was whether the experiment was performed on a marble table or a wooden table.

Ever since reading that story I tend to take more notes when doing stuff :-)

>1 Jahsena:

It should work now. There was an error in your cache which cleared easily. I'm going to look into how it started.

>7 timspalding: Thank you,