Chat history not loading
Occasionally the chat history stops syncing despite being signed in.
The thread titles are missing and the loading spinner loops endlessly. When posting new chat messages, it fails to update properly when the response is received. The chat response is shown but the stop button is still show and has to be pressed to post a further message in the chat.
Reloading the page resolves the issue but chats made during the state may be lost from my history or misfiled into the wrong thread history.
Log in to comment and vote
Comments4
Mark Florkowski
Just shipped a fixt to hopefully address this, feel free to reopen if you encoutner it again
Moccasin Meerkat
Unfortunately, this is still occurring.
I’ve captured some errors from the console log which might be helpful.
It also appears to only happen if I leave the T3 tab open and then hibernate the laptop (i.e., close the lid, disconnecting from Wi‑Fi, and resume later). Ideally, the session should time out after a while and prompt for reconnection.
What’s particularly strange is that the chat had thread titles before hibernation, so it seems to lose previously established context. I’ve also noticed that it switches the active model to Nano Banana Pro for the current chat, which is rarely the last model I used.
A further strange artefact is I can create new chats and change models. I even get responses from t3... but the UI keeps displaying a STOP button in the input panel (which I have to press before I can post a follow-up message in the thread). BTW I have far more than 3 chats in my recent history (daily T3 user).
Failed to load resource: net::ERR_NAME_NOT_RESOLVEDUnderstand this error
main-DE5J5bjq.js:12 TypeError: Failed to fetch
at main-DE5J5bjq.js:12:52030
at main-DE5J5bjq.js:12:52775
at Hs (main-DE5J5bjq.js:12:52847)
at Rs (main-DE5J5bjq.js:12:52018)
at async client (main-DE5J5bjq.js:21:18699)
at async main-DE5J5bjq.js:21:16129
at async u (main-DE5J5bjq.js:146:99319)
main-DE5J5bjq.js:146 [AUTH] Failed to refresh token: TypeError: Failed to fetch
at main-DE5J5bjq.js:12:52030
at main-DE5J5bjq.js:12:52775
at Hs (main-DE5J5bjq.js:12:52847)
at Rs (main-DE5J5bjq.js:12:52018)
at async client (main-DE5J5bjq.js:21:18699)
at async main-DE5J5bjq.js:21:16129
at async u (main-DE5J5bjq.js:146:99319)
u @ main-DE5J5bjq.js:146Understand this error
main-DE5J5bjq.js:19 WebSocket connection to 'wss://api.sync.t3.chat/api/1.30.0/sync' failed:
connect @ main-DE5J5bjq.js:19Understand this error
62main-DE5J5bjq.js:12 AbortError: signal is aborted without reason
at Object.onCancel (main-DE5J5bjq.js:18:13152)
at Object.o [as cancel] (main-DE5J5bjq.js:18:8386)
at Vc.cancel (main-DE5J5bjq.js:18:10502)
at Vc.fetch (main-DE5J5bjq.js:18:12161)
at main-DE5J5bjq.js:18:32892
at Array.map (<anonymous>)
at main-DE5J5bjq.js:18:32876
at Object.batch (main-DE5J5bjq.js:18:7271)
at sl.refetchQueries (main-DE5J5bjq.js:18:32805)
at main-DE5J5bjq.js:18:32664
main-DE5J5bjq.js:42 timestamp=2026-01-24T22:34:53.951Z level=INFO fiber=#477 message="Trace ID: 8faf6964050e12095e7d32599ab4ce94"
main-DE5J5bjq.js:42 timestamp=2026-01-24T22:34:54.391Z level=INFO fiber=#509 message=client.stream.firstChunk part="{
\"type\": \"start\",
\"messageId\": \"o4ptadPQUu1YDwWZ\"
}"
main-DE5J5bjq.js:12 AbortError: signal is aborted without reason
at Object.onCancel (main-DE5J5bjq.js:18:13152)
at Object.o [as cancel] (main-DE5J5bjq.js:18:8386)
at Vc.cancel (main-DE5J5bjq.js:18:10502)
at Vc.fetch (main-DE5J5bjq.js:18:12161)
at main-DE5J5bjq.js:18:32892
at Array.map (<anonymous>)
at main-DE5J5bjq.js:18:32876
at Object.batch (main-DE5J5bjq.js:18:7271)
at sl.refetchQueries (main-DE5J5bjq.js:18:32805)
at main-DE5J5bjq.js:18:32664
Mark Florkowski
Looking into this more
Moccasin Meerkat
No worries - its low priority as reloading the page resolves it.
If you need any logs or I can do anything to help if it happens again let me know.