Ever since last night I can’t do anything in AI Studio. I’m hoping it’s a temporary glitch but it has come at a really inconvenient time. No idea if it’s just a problem I’m having or if it’s widespread but it’s really disappointing.
1 Like
Hi @MikeyDebs ,
Welcome to the Forum!
We understand you disappointment. This seems to be a temporary issue.
Could you please try the below steps:
- Refresh your browser
- Try opening AI Studio in an incognito or private window .
- Sign out of your Google account completely, then sign back in.
Please let us know if still the issue persists.
None of those things helped but I have just discovered that I can work using 2.5 Flash, but nothing work in 2.5 Pro or 3 Pro. I have been working with those versions all week until yesterday. I’m not sure what changed between Tuesday and Wednesday.
Hi @MikeyDebs ,
Apologies for the delayed response.
Could you please share the below details:
- Step to reproduce the error
- Screenshot of the error message
same exact issue here, tried all of the above suggested by @Mrinal_Ghosh . Cant even deduce steps to reproduce error. no idea why this was happening as everything was fine for me earlier yesterday EST.
I’m having the same problem all day.
I
Same problem all day besides having chats blocked just for requesting a piece of jewellery with diamonds on it. makes zero sense
1 Like
Hi @Zade_Awad ,
Apologies for the late response! Thank you for flagging this issue. Are you still facing this issue? If yes, please let us know.
Happened to me for the past 2 days. Not useful if the message is only a “There was an unexpected error. Finish what you were doing.” and every retry fails.
These steps dont work. its like asking user with PC issues to reboot Windows.
What AI Studio should really do is to provide access to error logs, so that we can try to circumvent the issue. Though build for aistudio is a prototyping tool, it is also important as we invest hefty hours and get stuck.
Finally, issue persist even after migrating the app to a brand new google account (without quota or browser cache issues). This is clearly in the state of the project, where it got corrupted or code fragments killing build’s interpreter.