This looks like a backend authorization issue rather than a local browser or Drive sync problem. Since the files remain in Drive but AI Studio cannot read them, the most likely cause is a broken token or scope mapping between your account and AI Studio’s backend. You’ve already tried re-authorizing from the Google Account permissions page, but I recommend also signing out of all Google sessions, clearing cookies for ai.google.dev, and logging back in to force a fresh OAuth handshake. If the issue persists, open a support case via Google Cloud Console > Support with your project ID and affected file IDs so the team can check token state server-side. Keep your “Send Feedback” report reference handy, as engineering will need it to correlate logs.
thanks. Have done this and am waiting for a reply from the the support team. Every day i receive an update that basically says - ‘working on it will get back to you tomorrow’
I lost all the work I did from Thursday December 4- thru Friday Dec 5th. I am still unable to open those files in Google Drive or AI Studio. They return a ‘page not found’ message. It was the latest version of my platform and I had just deployed it on cloud run. Luckily I had dowloaded all my code to my laptop and by opening an earlier version was able to rebuild it. I opened this earlier version and kept it open in AI Studio for several days for fear if I closed it I would not be able to reopen it. I now hold my breath every time I open a file in AI Studio, and don’t relax until it is fully loaded. To this day I do not understand how this happened.