Your AI does not use Leaf
- Leaf is not on in this conversation: turn it on in the tools menu, then send the message again.
- You answered no when it asked to use Leaf: send the message again and allow it.
- It answered without Leaf: ask again, starting with "Use the Leaf connector".
- It is connected to another Leaf account: disconnect Leaf in your AI and connect it again with the right account.
- You cannot find where to add a connector: most AIs need one of their paid plans for it.
Leaf refused something
Leaf answers your AI with Refused (code): what happened, followed by a hint saying what to do next. Your AI usually follows the hint by itself. The common ones:
| Code | What it means |
|---|---|
org_required |
You belong to several organisations: say which one. |
project_ambiguous |
Several of your organisations have a site with that name: say which one. |
revision_stale |
Someone changed the site since your AI read it. It reads again and retries. |
role_insufficient |
Your role does not allow it: ask an owner or an admin. |
promotion_needs_human |
This site waits for a person to put it online, from the dashboard. |
limit_exceeded |
The change goes past a limit. Nothing was written. |
usage_exhausted |
The organisation used what its plan includes and its credits: builds, server code and AI pause, pages stay online. An owner or an admin adds credits in Billing. |
A preview fails
When a preview does not build, your AI gets the end of the build log and fixes the code. If it stops there:
Tell your AI
With Leaf, the last preview of my site failed. Find why and fix it.
The site does not show my change
- A change your AI made is on the preview until it is put online.
- Texts changed in the dashboard reach the online site once published and after Update the site.
Still stuck
In the dashboard, Help and feedback opens our support, where you can write to the Leaf team: support.getleaf.team.