Yes, this is a long-standing problem with the original database design. What we're seeing is that a long query will lock a table, making it impossible for anything else to update that table until it's finished. If you are trying to post to that table, and it's locked, the appserver you're on thinks it has lost its connection and will probably try to restart itself, thus logging you out. This is different than when you log in without setting "remember me" and then get pushed to another server if your current server maxes out its connections.

Our plan for addressing this is to upgrade the database and migrate to a new engine that doesn't lock tables this way. However, because of the design of the database, this is proving to be quite complicated. It's a bit of a vicious circle.

I'm sorry it's such a slow process, it's definitely the major project we're working on right now.

By "getting signed out" you mean ending up on the tribe beta page when you want to submit the response you just wrote up?
Yeah, that one is very annouying, I have worked out the solution to click back to the page with my draft, copy the draft and paste it into a mail frame and save it in email, and once I get back into tribe I can copy and paste it from there (email frames work much faster than formating a Word doc etc.) , But I agree, it sucks. Is this the bug you mean?