>I have to agree, it's hard to pin down firm examples but I'm pretty sure from time to time (maybe a couple of times per month?) I've seen replies come up at a new UT login without having seen the original message (I believe the same as what Mike is seeing). In those cases I use the "view entire thread" button to view the top message.
>
>I have 3 long-inactive accounts twitted, but no other filters set.
>
>FWIW I believe (but not 100% sure) the ONLY messages I miss this way are top messages created since my last manual or automatic "refresh". Just maybe, it's something related to retrieval of new, top messages (?)
>
>One thing I regularly do (with FireFox) is I navigate away from UT for a while, long enough that no doubt UT times out on me being "logged on". However, I'm lazy, so if I want to go back to the UT I don't log in again, I use the back button on the browser to go back to the most recent UT page in my history. That *seems* to work OK, the number of available new messages seems to be correct but I wonder if that's screwing up the refresh/saving mechanism somehow.

It could create some unexpected behavior as a site is meant to move forward and not backward. When doing so, more than often, cache will be used and this is where problems will start. The proper way to use the site is to log in from main page and work from inside the support area.

For those that might have seen something like that, keep in note also that a double click fast on the login button could create a situation that the first click sends a message to load the interface from the last point of message having been retrieved. But, in the same second, the second click does the same thus returns pratically almost no message, unless one or two messages just arrived within that second.