Google AI Studio Build: “An internal error occurred” and “Ran for 0s”

AI Studio Build fails instantly with “An internal error occurred” or “Ran for 0s”? Try a new chat inside the same app and preserve project files.

Quick answer

When a Build prompt fails at Ran for 0s, save the app's current files and error ID before changing anything. The error has been reported alongside Invalid argument and Permission denied; those messages do not prove one shared cause. Start with a new chat inside the existing app, so you can test the assistant without replacing the project.

Exact message

An internal error occurred
Ran for 0s

Guidance in the Google AI Developers Forum

In an October 28–30 Google AI Developers Forum discussion, a forum support responder advised New chat → Start new chat at the top of the Build chat panel, then sending the prompt there. The responder said this keeps the existing project files and recent changes. For the separate Permission denied message, the responder suggested disabling ad/privacy/script-blocking extensions or trying an incognito window. If the error persists, they asked for the Applet ID through a private message. These are support instructions in that thread, not a guarantee that every Build error is fixed.

What users actually saw

The first user said even a simple diagnostic prompt failed at Ran for 0s while the app preview still worked; refreshing and switching modes had not helped. A second user reported An internal error occurred, Invalid argument, and Permission denied on an existing website project; refreshing and changing networks did not help. Both wanted to keep their work. If a fresh chat in the same app still fails, record the Applet ID privately, the error ID, time, and whether another project works. Do not publish private project identifiers in a public forum.

If the response explicitly contains 429 RESOURCE_EXHAUSTED, use the Gemini API limit checks.

Frequently Asked Questions

Will “New chat” delete my app?

The forum support responder says a new Build chat inside the same app keeps its project files and recent changes. Confirm you are opening a new chat in the current app, not creating a replacement app or restoring an older checkpoint.

Does paid Gemini API access cause this Build error?

In that thread, the support responder told one user that activating the Gemini API paid tier was not causing those errors. That answer concerns the reported case, not every billing configuration.

Should I use the Gemini API 503 guide?

Only if your API request actually returns 503. Ran for 0s in the Build panel is a different symptom; the 503 guide explains the API case.

Sources

Google AI Studio forum support and first-hand user reports: Build mode thread. The support reply and user reports are labelled separately in the body.