Issue: Saving to Google Drive Fails Intermittently

Hello AI Studio Team,

I’m experiencing an issue where saving to Google Drive sometimes doesn’t work.

When I try to save, it shows the “Saving to Drive…” message, but it seems to get stuck there and never actually completes. The file doesn’t end up saving to my Drive. This happens occasionally.

Could you please look into this?

Thanks

2 Likes

Hi @grav,

I may not be able to reproduce the issue but thanks for reporting the issue, I will escalate the issue to the team

Thank you

this happens to me too sometimes. and Since yesterday, saving has also stopped to autosave.

Hi @grav,

To help us understand the issue, could you please provide the length of your prompt and specify if it was text-based or multimodal? Any other details about the scenario would also be helpful.

Thank you

Thanks for getting back to me. To answer your questions:

  • The prompt length is typically in the range of tens of thousands of tokens.

  • It’s a multimodal prompt, involving both text and images.

This happens to me often, and I only work with text with Gemini 2.5 Pro Preview 05-06. After about 10K used tokens, the chances of successful (auto-)saving to Drive are low. The spinner just constantly spins, and if I navigate away from the page, I’ll lose the updates to the prompt.

Got the same problem since yesterday. As long as I don’t refresh, everything’s fine, but nothing is being saved to Drive:

  • No Cross platform availability
  • If I quit the Chrome session, the day’s prompting and results are lost
  • A bit of a pain…

Typically starting a new conversation after around 100k tokens, I start to get increasing misbehaviour from then onwards - main use case is for speeding up note processing and reformatting; the greater the number of tokens the higher the chance it gets confused between images, and from then on it typically goes downhill (less and less reliable, and will acknowledge errors, says will correct them…and then repeats them, etc, etc)

same problem. serious issues with prompt autosaving, autosaving settings, and prompt file saving in google drive (way too many folders)

ezgif-68eee08d0dd306

(this is a GIF video file, click it to watch)

I hit this bug a few times already.
It’s soooo annoying. Turning the autosave on and off doesn’t help.

@Siva_Sravana_Kumar_N

+1.
Same issue as reported by others and as the animation above. I first noticed it last week. It seemed to be OK yesterday but is failing today.

Furthermore, after I hit this, I am not able to use copy the context window to save it, nor branch the context window.

This is awful.

ezgif-5f22d8134e9608
(this is a GIF video file, click it to watch)
@Siva_Sravana_Kumar_N

Same issue, happens every 5 or so prompts and is incredibly frustrating.

same here, happens on almost every session after a few chats. I’ve just copied the Rest JSON for my session, I’m going to see if I can resurrect the chat using this?

*Edit: It works, I created a new chat prompt, "can you resurrect this chat?

I can assure you this happens frequently. Like everyday. Gotten to the point where using AI Studio has become too risky. If I go away and come back, there is now a 50-60% chance the chat is gone. I think it happens when the “Autosave” feature just is spinning idling, looking like it’s doing stuff, when really it’s just not saving your stuff/actively deleting things.

Can you explain more of this workaround? Did it require having exported the JSON from the previous chat prior?

This bug is DESTROYING User Experience and almost makes the product unusable. Please fix Google! We all want AI Studio to work as intended.

Did you find Vertex AI with the same issue?

I am not advertising; I am just finding a more stable service.

Can confirm this is still happening. Extremely frustrating, I had gotten 100k+ tokens into a chat and the autosave had only captured my initial messages with the uploaded context files. For reference, this was a multimodal chat. Am going to try using the Rest JSON file to see if I can replicate the chat again.

Hi all,

Can you all DM me with your Google Project #.. As there were multiple types of failures, it would be easy for us to debug based on your Project #s.