override agent cache for some users/forms

[dustymc]

          I think some of these are due to lags in the cache. I have added agents and for a while, search won't find them except when I search the EXACT preferred name. I can see how people would add someone again....this needs training.

Originally posted by @Jegelewicz in #7649 (comment)

[dustymc]

I did write the possibility of changing the cache time (including to zero) into the API, so there's no technical trick in allowing (defaulting, whatever) "us" an override. That could also be used to melt the server, so guidance needed.

Cached data will also slow repetitive selection, and one agent doing lots of stuff is a very common situation.

I'd still very much like timely guidance, but this is very clearly making messes and angering users. I'll do something....

[dustymc]

There have been a lot of timeouts in the logs, I'm reducing the number of available rows an operator can return for next release. It may be necessary to search for a more specific string in order to find what you're looking for. (The actual number of rows is data-dependent and will vary for nearly every search.) I

I can't see what's causing the timeouts, only the errors. Please let me know details if you are getting timeouts, I may be able to tune the database.