When Messages reports Conversations could not be loaded, use the retry control beside that error. The page has not established that there are no conversations.
Check your connection and account context if the error persists. Previously loaded conversations may remain visible while a newer fetch fails, so do not assume every displayed preview reflects a successful latest update.
After a successful retry, clear the search and choose All conversations before looking for a missing thread. No conversations found is a search result, while the loading error concerns the list itself.
If you need support, describe the list error and the account or workspace involved. Include the subject of the expected conversation when known. Avoid creating a new thread solely because the original list could not load; that can create duplicates once the connection recovers. If communication is time-sensitive, use the published support route and mention that Messages is unavailable so the team understands why you are contacting them elsewhere.
Was this article helpful?
Tell us whether this answered the question you came with.