Hey everyone,
Since yesterday, I’ve been having a weird issue with my AI Studio. A lot of my old chat conversations are acting strange.
Here’s what’s happening:
-
I can open my old chats just fine.
-
But the token counter at the top of the chat is missing. It just doesn’t show up.
-
When I type a new prompt, the “Run” button stays grayed out (disabled). I can’t click it at all.
The weird part is, if I start a brand new chat, everything works perfectly. The token count is there, and the “Run” button works.
Is anyone else seeing this? Did Google maybe disable or change something with older chat histories?
I’ve attached a couple of screenshots to show what I mean:
-
One showing the missing token count in an old chat.
-
One showing the disabled “Run” button after I type something.
Thanks for any help or info!
ps：
4 Likes
I’m facing the same problem. And that’s what I came up with
I’ve found a temporary workaround for this issue: we’ll use keyboard shortcuts to send requests
Alt+Enter
The message is sent to the chat but doesn’t trigger a response, so it needs to be run manually.
—and then click on the logo to re-run [run the prompt] the stars.
5 Likes
Hi @mygram21,
Welcome to the Forum,
Thank you for flagging this. I have reviewed my previous conversations and can confirm that all functionalities, including the token counter and Run button activate immediately after I type a new prompt.
To help us troubleshoot this issue, please provide the following details:
- What browser and version are you currently using?
- Does the problem continue if you try a different browser or an incognito window?
Appreciate the follow-up! Nope, still not working. Tried it on Chrome 141.0.7390.123 and in Incognito mode, but it’s still kinda borked. Just gonna stick with the temp fix that was posted earlier for now.
Yes this seems to be some bug. It is not browser specific but I am using mozilla. The fix of editing older message and then running works but can’t send new message because of the button and the shortcut command+enter is disabled.
Hello !
I’m experiencing the same issue. For me, it happens only where token count is > 400k. I have done a test with a prompt which I branched and what happened is that at around 375k token, the token count finished loading but on a simple subsequent refresh it wasn’t working anymore. My logical conclusion is that either the bug is intermittent or perhaps it’s like a timeout where the “count” gives up.
It happens in Firefox 144.0.2, Firefox Dev Edition 145.0b8, Chrome 141.0.7390.123, latest Chrome (as of 31 Oct 25) on Android, so everywhere.
The screenshot I add shows that the input/output tokens have been counted, yet this doesn’t appear in the small icon on the top. This bug appeared simultaneously with the scrolling but of the 27th or 28th of October where the discussion was jumping all over the place.
Ah… I am having the same problem and so it’ s likely a broader issue and not a setting (or some strange token issue). I posted the following in the Gemini forum and someone suggested I post it this forum. Sounds like this is a problem that started a couple of days ago and affecting more than just me! I have some old sessions that still work. See my scenario below and let me know if there is a pattern.
I’m a Google AI Pro subscriber and am experiencing a recent issue in AI Studio where the Run button and Ctrl + Enter functionality have been disabled in 3 out of my 9 active sessions.
Details
-
The affected sessions are part of a 4-part series following a consistent naming convention (e.g., Phase 1, Phase 2, Phase 3, etc.).
-
The most recent session in the series (Phase 3) still functions normally.
-
All unrelated sessions outside of this series are also working as expected.
-
Token usage is well below the 1 million-token limit:
-
Session 1: ~600 k tokens
-
Session 2: ~500 k tokens
-
Session 3: ~33 k tokens
Troubleshooting Steps Attempted
-
Cleared browser cache and cookies
-
Tried multiple browsers (Chrome, Edge)
-
Tested in Incognito/Private mode
-
Submitted feedback through the in-app feedback option (no response yet)
Summary
The issue appears to be isolated to a subset of related sessions. It’s unclear whether this is a token-count, naming convention, or session-state issue.
Has anyone else encountered similar behavior, or does anyone know of a workaround or method to re-enable prompt execution in affected sessions?
Thank you in advance for any guidance.
2 Likes
I have the same problem with promts over 500.000 tokens. I tried different browsers.
2 Likes
Three weeks with this problem and zero urgency from support. Google confirms their services are operational, so the issue must be on your side.
2 Likes
