I already sent and example, idk why the fix is taking so long, I need to be able to use my chats now. The scrolling bug took faster to fix.
4 Likes
Weird thing that this bug started when the scrolling bug ended, lol.
2 Likes
@Mrinal_Ghosh please look into this issue already its been unresolved for literal days, almost a week now. At least give an update on the situation or if anything else is needed to help clarify the issue.
2 Likes
Cant we email the devs directly?
I did the procedure as you wrote. I scrolled through the chat before the start of the correspondence and I have the poison message button active and the tokens count appeared, the correspondence is also saved. But that was the end of the joy((( After refreshing the page or you wrote some kind of message, the endless loading appears again, the button is deactivated. You need to scroll through the whole conversation again from the beginning and write the message again. Then I noticed something else. You don’t have to scroll to the end of the chat. The chat starts working before scrolling through half of the conversation. See how it works for you. I checked on Windows 11 pro. I haven’t checked on android.
I don’t know what it’s related to. Maybe the company is forcing you to buy a paid subscription, or this is really a bug.
1 Like
It only affects old chats, the newer ones work fine no matter how many tokens its definitely a bug maybe you can try emailing Google about this, they’re taking way too long to fix this bug when they instantly finished the scrolling one.
1 Like
I’ve experienced this bug twice. In the first chat, I waited for 5 days, but the token load wouldn’t stop. I tried branch mode, but it still didn’t work. I tried all the available methods, but to no avail. Until I decided to create a new chat with the same context as before. And then it happened again, just like that, the Load Token bug wouldn’t stop. Until I read your method, and it worked. Big Respect! Thanks.
But is this a bug or what?
It’s very annoying when you’ve already done a long task and have to repeat everything with a summary.
1 Like
Did you try to import your chat into a new fresh chat?
2 Likes
So many days have passed, and for reasons unknown, no official representative has attempted to advance the resolution of this issue—not even by taking steps like asking for more detailed information from everyone involved.
“White_ai” proposed a solution that was short-lived and impractical (though it did resolve the issue of being unable to continue asking questions). However, given that problematic dialogues consistently occur after substantial token usage—typically indicating deep engagement with a specific question or topic over multiple rounds—you cannot risk subsequent conversations failing to save. This persists unless the root cause is addressed: the bug is fixed.
Methods like copying problematic conversations to new threads or attempting forced input via shortcuts cannot circumvent the fact that a bug exists, specifically concentrated in conversations exceeding 300k tokens.
Creating a new conversation and casually chatting with the AI for a few rounds does not trigger the issue. This explains why the official support team initially reported being unable to reproduce the problem—the conditions required to trigger it simply weren’t met.
As of now, we remain unaware of what exactly is happening.
Perhaps everyone is on vacation?
3 Likes
This thread won’t close until this is fixed, I am disappointed with the Developer team for not responding, are they all on vacation? Who knows but I’ll keep replying onto this thread until he issue is fixed completely.
4 Likes
Must be some long vacation lol
2 Likes
hope it gets fixed soon
4 Likes
For the love of God @chunduriv please come back to me, are there any updates on this bug fix? Its affecting my workflow.
2 Likes
This one worked for me with chat having token usage < 300k
1 Like
Is there an easy way to do this on a long chat? because I have tried selecting all the text but all I get is the text thats on the screen at the moment, and sometimes the chat are VERY long.
2 Likes
Try scrolling up to the beginning of the chat then down until you reach the end, repeat until you can chat again. This is a temporary fix.
2 Likes
I’ve found out that if you make a copy of the chat, the copied chat would have the newer inputs and outputs too. This is a temporary measure for the stuck chat not saving the inputs and outputs generated (by the Alt+Enter and Sparkle Run measure) while it’s stuck on waiting for content to load.
However, note that current Make a Copy feature doesn’t allow for opening in a new tab, so it basically overwrites your current tab, which means the stuck chat of course is switched off, with all the new content gone. So every make a copy comes with a risk, that if the make a copy fails to include new content, you lose it all.
1 Like
I’ve tried your approach(scroll up to the beginning of the chat) and it works!
2 Likes
1 week and 2 days since the hug happened, there’s still no fix yet. I’m waiting until there’s actually an effort for the Google Devs to finally return.
3 Likes