I am writing to report a critical issue involving the loss of a branched conversation and persistent access errors in Google AI Studio. The content within this branch is extremely important to me! Please help me! 
Here is a detailed timeline of the problem:
-
Branch Creation and Accidental Deletion: I previously created a branch from a main conversation. Later, I accidentally deleted this specific branched conversation from my conversation history list.
-
Prolonged Access via Direct Link: For a significant period after the deletion from the history UI, I could still successfully access, view, and interact with the contents of this branched conversation using its direct link. I was also able to save new prompts within this branch without any issues during this time.
-
Sudden Onset of Errors During Active Session: I was actively working within the branched conversation (accessed via the direct link) when the problem began. The conversation itself was still responsive and generating responses. However, it appears the error tip:
failed to save prompt. requested entity was not found,when I tried to save the latest prompts handed, I falied and still received the error . -
Complete Data Loss Upon Refresh: After encountering the initial save error (
failed to save prompt. requested entity was not found), the branched conversation interface remained open and I could still scroll through our entire conversation history within the window. However, no new interactions could be saved. In an attempt to resolve the save failure, I manually refreshed the page. This action resulted in the complete and permanent loss of access. The page loaded to show the final error message (Prompt cannot be accessed.The requested prompt does not exist or you do not have access. If you believe the request is correct, make sure you have first allowed AI Studio access to your Google Drive, and then ask the owner to share the prompt with you)and the entire conversation history, which was just visible moments before, is now gone and unrecoverable through the UI. The link has been fully invalidated. -
Final Access Attempt Failed: Following the complete loss of the branch page upon refresh, I attempted to regain access by going back to the original parent conversation and clicking on the link there that was previously used to create and access this specific branch. This link, which had functioned perfectly until the moment of the save error, was now also completely inactive ,can not redirect to anypage.
6.Data Discrepancy in Google Drive: I have verified that while the original parent conversation is still present and accounted for in my Google Drive, there is no record or trace of the branched conversation whatsoever. This confirms the loss is specific to the branch entity and not a general Drive sync issue.
I urgently request assistance in investigating whether the data for this specific branched conversation can be recovered .Please help me ! It’s very important to me !!!
Thank you for your immediate attention to this serious matter!