"flush did not complete" errors
When a session browser is open during the login of a second session, in order to determine the session transaction mode to set the radio button correctly, the browser must make a server call. This call uses the default timeout set in gbxEvaluateOnTimeout, which is 1.5 seconds. If the server call takes longer than this and times out, there is a risk that unwinding the stack can be incorrect, resulting in an error "The previous flush didn't complete - errors may result unless you log out and back in". Since the session must log out, this is a serious problem.
As of version 7.2.1, the timeout has been increased to 5 seconds. Also, we no longer synchronize session state which was a part of the "the previous flush didn't complete" error. However, errors can still occur if the timeout is reached.
Workaround
If you are logging in programmatically, avoid having a session browser open. When using the session browser to perform logins that may take a long time (such as on very heavily loaded systems), increase the timeout in gbxEvaluateOnTimeout.
Last updated: 10/22/08