AI Studio AutoSave Failure – Conversation Progress Lost After Refresh

I am encountering a critical issue concerning the preservation of conversations and data within the platform.

While working on a project in the AI Studio platform, where I am developing an application, I engaged in a continuous dialogue spanning approximately three weeks. This conversation involved the utilization of around 800,000 tokens, encompassing files, code, and analyses that I automatically uploaded to the model.

However, upon refreshing the interface (due to unresponsiveness), I discovered that the conversation had not persisted from my last point of activity but had reverted to an earlier state (approximately 600,000 tokens).

Upon inspecting the file’s version history in Drive, I observed that the most recent saved version dates back to the previous day, and I have been unable to locate an updated iteration.

This is despite the fact that autoSave is enabled, and I have witnessed synchronization occurring at each step of the conversation.

Furthermore, I had refreshed the interface several times earlier today, and it consistently resumed from the exact point where I had left off, until this most recent occurrence.

It was only upon this subsequent refresh that the conversation reverted to the state of the previous day.

This issue is resulting in the loss of significant information that I have invested considerable time in developing, and it is negatively impacting my workflow. I request clarification regarding this problem and a proposed solution that will ensure the continuous and accurate preservation of data.

The ramifications of this issue include:

Loss of critical content generated after 5:00 PM yesterday, which was not saved.

Impairment of project progress and my work hours.

I implore you to investigate this matter and, if feasible, recover the lost data.

This is of utmost urgency to me.

Thank you for your assistance.:folded_hands:

2 Likes

Hi @user1887, Welcome to the forum!!

Thanks for flagging. Also, i hope you didn’t refresh until it generates whole response, otherwise it won’t be able to. Is it happening with only one of the prompts or other prompts as well??

זה פעם ראשונה שזה קרה.
ואכן, הוא יצר תגובה מלאה לפני שזה קרה

בתאריך יום ד׳, 14 במאי 2025, 12:43, מאת Govind Keshari via Google AI Developers Forum ‏<notifications@discuss.ai.google.dev>:

I’m having the same issue due to the fact that AI Studio often fails to save updates to a prompt to Google Drive.

Could it be due to some rate limiting on the GD’s side?

Hey folks, Escalated the issue with our internal team. Will ask any extra info required here.

Thanks

2 Likes

Don’t know if it’s somehow connected but I have lost (i. e., it didn’t save) a significant part of my dialog today which was generated after temporarily losing an internet connection (I hadn’t checked whether it has successfully autosaved though, unlike the OP)

Hi folks. This just happened with me and I lost part of the chat from the yesterday. Man, I dreamed about the follow up conversation then I wake up eager to keep chatting but the messages aren’t there anymore. Does anyone know if it’s possible to recover it?

I myself have experienced this twice in the last two days. One project was at 800,000 tokens that I’d been working on for three days, and unexpectedly Google AI Studio crashes and I cannot recover that work. Today, I restarted that work, figuring that I would make sure that auto save was placed correctly. It was. I got to 600,000 tokens and Google crashed again. It’s not saved to my drive and I’ve tried an incognito browser. I’ve deleted my cache, my browsing history to see if that was the issue, and it is not. This is extremely frustrating and disappointing. What makes it worse is that there is no one you can reach out to other than coming to a public forum and “Modified by moderator” Google about really something that should be taken care of, which is an archive or some kind of process for recovering drafts. It’s unbelievable to me that there’s no way to recover files that have been worked on persistently for over 500,000 tokens. If someone can reach out to me and give me some idea on what can be done, who to speak to, or a better process, which I find to be challenging to think of when you have auto save and everything is supposed to be saving to Google Drive, how possibly at between 600,000 to 800,000 tokens, your project can just vanish into thin air.

2 Likes

Hi everyone. I have experienced the same issue of losing chats in the last week.

I have been both losing complete conversations, and parts of conversations. Conversations that are available in my history for the span of a day, and than get lost.

I thought this had to do with my autosave setting - this was turned off all of a sudden around the I/O updates, and I had to put it back on. But it also happened afterwards.

Also interesting: since it happened for the first time I got more cautious, so I made a copy of a conversation to prevent this from happening. It turned out that in both the original and the copy of the conversation, all the chats after the exact same message were lost.

For users experiencing the same problem: I am turning towards saving prompts + outputs in my notion as backup pages (copy markdown is your friend here).

For google employees: Please update when this issue is looked into, if there is an update about it, what other actions can be done to prevent this from a user perspective.

2 Likes

Yep, it happened to me multiple times as well. Auto save was definitely ON, the conversation just went back in time. Super frustrating when they loose context after building great things !
There definitely should be a way to recover these conversations !

1 Like

Same exact thing here

1 Like

Me as well, I am experimenting the same issue. For some reason, the auto save which was always on is not working for me anymore. Mine is stuck on saving. I don’t know why.

And I only realized it’s a day later when I came back to work on my project. So the trick was to save by copy pasting the text in a Word document until this thing is solved.

Edit :
I believe I found something that worked for me (at least until now).

  1. Disable the auto-save (if you have it turn on). It will disable for all chats.

  2. Make a copy of this prompt (aka chat conversation) and save manually (since we disabled the auto-save). This is for backup purpose in case it doesn’t work. This might be optional but I wasn’t sure so I did it anyway.

  3. From time to time, click the save button yourself and wait for it to finish saving, then proceed with your work.

I believe this a temporal solution.

I’ve had this happen to me twice now (to my knowledge).

I haven’t experienced any crashed and this isn’t due to the prompts not saving. They have been over several days.

One project I had come back to several times over the course of a week or two. The only versions I can find for it now were only created on the day the initial prompt was generated. All versions since are missing, not in the trash just gone.

Autosave is enabled and I’m 100% certain that versions have saved numerous times since. Even the media I’ve uploaded to those conversations is still in the google drive but the chat history is gone and nowhere to be found.

I’ve spent an enormous amount of time on a conversation. Autosave is enabled. I can see the conversation in my ‘Activity’ but can’t view the conversation in any other way.

These kinds of issues makes this product unusable for any serious cases.

The AI Studio full stack is comming ?
The prompts for mobile app only generate a react app , my prompt definition is incorrect defined?
A part of the prompt defined is:

# Native Mobile Survey App Specification  
**Project:** Mobility Survey Pro  
**Platforms:** Android (Kotlin) & iOS (Swift)  
**Minimum Versions:** Android 14 (SDK 34), iOS 17  

## Technical Architecture  
```mermaid
graph LR
    A[UI Layer] --> B[Domain Layer]
    B --> C[Data Layer]
    C --> D[Local Database]
    C --> E[Remote Server]
    
    subgraph Android
        A --> Compose
        D --> RoomDB
        E --> KtorClient
    end
    
    subgraph iOS
        A --> SwiftUI
        D --> SwiftData
        E --> Alamofire
    end