>>>>I am not sure what that means, but all I can say it everyday I notice threads half started, without me seeing the original post. I don't know how that happens, but it does.
>>>
>>>What you get is the new messages. A message can be either a thread (top message of a thread) or a message within it. Thus, a first message of a thread is the top layer of it. Underneath can be several layers of messages. So, among new messages can be new threads, where you will see the first message of a thread, or ongoing thread messages, where you will see new messages from the related threads.
>>>
>>>Thus, if you have already read the first message of a thread, it will not appear in the next refresh or at the next login.
>>>
>>>When reading a message, as previously mentioned, if this is not the top message of the thread, which usually starts with RE:, there will be a hyperlink in the thread title, when viewing the message, to jump back to the original message if you wish to do so.
>>>
>>>Let me know if you need more information.
>>
>>All I can say, is, this is not what is happening for me. Perhaps that is your perception, but not mine. I log on one day, and go back one day, and see messages I never looked at (either reading them or not).
>
> I think a few slip through the cracks, but I don't know how. I've experienced (and posted here about it) some missed messages myself in the past. It's not everyday but it's aggravating when it happens. Sometimes the messages are replies to me and sometimes not.

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.