Troubleshooting: Godot, AI & Provider Errors

Find the message you see in chat below. Use the buttons on the error card when available.

“The provider rejected this request”

Read the reason on the error card. If your request was blocked, try rewording it or click Switch model. Review any changes already made before continuing.

If the provider is temporarily busy, try again shortly.

“Ziva couldn’t read a project file to save a restore point”

Make sure your project files are available on your computer and that you can open them. Switching models will not fix a file-access problem.

If your project is in OneDrive:

Make sure OneDrive is running and signed in.
In File Explorer, right-click the project folder and choose Always keep on this device.
Wait for the folder’s solid green circle with a white checkmark, then click Retry in Ziva.

This keeps a local copy without moving your project or stopping OneDrive syncing. See Microsoft’s OneDrive instructions .

You can choose Continue without undo and confirm to send this message without a restore point. Undo cannot revert changes Ziva makes for that message. Earlier restore points are kept.

If it still fails, try a project copy outside OneDrive or use Send a report.

“Your disk is full, so Ziva couldn’t save a restore point”

Restore points can be stored on your system drive (usually C: on Windows) even when your project is not. Free up space on both, then click Retry.

Damaged history, missing Undo, or an unresponsive editor

If automatic recovery fails, click Retry or, when offered, Continue without undo. Send a report if retrying does not help.

Reset damaged checkpoint history

If Ziva says checkpoint history is damaged:

Stop every running chat.
Choose Reset checkpoint history… and confirm.

This keeps your project files, chats, settings, and a backup of the old history. Messages from before the reset lose their Undo restore points.

If Undo is unavailable for an older message, see Undo and checkpoints. Resetting checkpoint history is different from resetting all Ziva data.

If Godot is unresponsive, wait for it to respond before retrying. Save pending work before restarting the editor.

Scene creation fails or a tool repeats with the same arguments

If Ziva says Godot could not parse a scene, ask it to fix the reported scene error instead of repeating the same edit.

A message saying a tool was called 3 times in a row with the same arguments means Ziva stopped making progress. Ask it to try a different approach using the reported error, or choose Switch model.

“search_text not found” when editing a file

Ask Ziva to read the file again before editing it. If the same text appears more than once, ask it to include more surrounding lines so the edit is unique.

“Cannot save res://project.godot”

Keep Godot open so you do not lose unsaved settings. Switching models will not fix this file-access problem.

Try saving in Project > Project Settings. Check Godot’s Output panel for the save error.
Make sure project.godot is not read-only and close any program locking it.
If your project is in OneDrive, make its files available locally as described above.
Once Godot can save the settings, click Retry in Ziva.

On Windows, check Windows Security > Virus & threat protection > Protection history for a blocked Godot write. Follow your security policy for allowing the trusted Godot executable. Do not disable antivirus or folder protection.

If saving still fails, use Send a report. Review reports for private information before sending.

“The model this chat is set to is no longer available”

Choose an available model before sending another message. If the model list looks out of date, save your work, restart Godot, and check for a Ziva update.

“The model provider failed” or Smart stops answering

Wait for the current attempt to finish before sending the same message again. If an error card appears, click Retry. If it keeps failing, click Switch model and continue in the same chat.

Still stuck? Send a bug report after reviewing it for private information.

“Daily limit reached” / “Weekly limit reached” / “Monthly limit reached”

You’ve used up your plan’s allowance for that period.

Wait for the limit to reset, or click Upgrade plan.
Click Switch model to use one from your own AI subscription or a local provider, if available.

See Usage Limit Best Practices.

Your connected Claude or ChatGPT account hit a limit

Your own AI subscription hit a limit or refused the request.

Wait for that account’s limit to reset.
Or click Use Ziva usage to use your Ziva allowance instead. If the model needs a higher Ziva plan, Ziva shows upgrade options.

“Your connected ChatGPT account can’t use this model”

Choose Switch model, or Use Ziva usage when offered. Sending the same request again will not give your ChatGPT account access to the model.

“Claude Fast mode requires usage credits”

Click Disable fast mode and retry to keep using your connected Claude account without Fast mode. This does not add credits or switch to Ziva billing.

“The model provider refused this request”

Read the reason on the error card. For an OpenRouter spending limit, check your OpenRouter credit and budget, not your Ziva plan. Switching models on the same OpenRouter key may still hit that limit.

You can also click Switch model to choose a different connection.

“The account behind this model was refused”

For Claude Code, Codex, or OpenRouter, click Reconnect provider and sign in again.
For Ziva models, click Sign in.

“This conversation is too large for this model’s context window”

Click Compact conversation to shorten the chat history.
Or click Start a new chat or Switch model to one that can handle more text.

Ziva only sees the start of a long tool result

Ask Ziva for the part you need, such as “Show me only the errors about the player scene,” rather than the full result.

“A message in this conversation is too large for this model’s context window”

One message is too big, so compacting the chat will not help.

Click Start a new chat, then send fewer files or a shorter prompt.
Or click Switch model to one that can handle more text.

”… needs Ziva Pro”

If you’re signed out, sign in so Ziva can check your plan.
Click Upgrade plan, or Switch model to one your plan supports.
You can also use your own AI subscription.

Billing or checkout problems

If checkout or plans will not open:

Make sure you’re signed in.
Make sure a default browser is set and you can reach the Ziva website.

A subscription payment failed

Choose Update billing at https://ziva.sh/account#subscription to fix the payment. Paid features return when payment succeeds.

Check your subscription status before paying again. Updating a card does not restart a canceled subscription. Contact support if the status looks wrong. Never send card numbers or security codes. Your connected AI providers handle their own billing.

Local models (Ollama / LM Studio) don’t appear

Make sure your local model app is running and has a model installed. See Local Providers troubleshooting for setup help.