Your AI app passes these messages on as it gets them, sometimes in its own words. The parts in brackets are filled in with your site, tool or numbers.
Warning When a call that changes something times out or fails on its way back, the change may still have happened. Check FlitAgent → Activity and Approvals on the site before you ask again.
Choosing a site
- “No site is connected to this flitagent.com account.” Connect one from FlitAgent → Connect in its wp-admin.
- “[site] is not a site on this account.” The app named a site your account does not have. Use a name from the list in the message, or ask the app to call
list_sites. - “[site] matches more than one site on this account” Name one of the listed sites exactly.
- “Name the site to use in the site argument” Your account has more than one site; tell the app which one.
- “This site is not confirmed yet” flitagent.com has not reached the site since you connected it. Open Check the connection on flitagent.com in FlitAgent → Connect.
- “[site] is disconnected from flitagent.com.” Connect it again from FlitAgent → Connect in its wp-admin.
- “[site] disconnected FlitAgent in wp-admin” The site refused flitagent.com’s requests for a week, usually because it was disconnected in FlitAgent → Connect, or the same address was connected to another flitagent.com account. Connect it again from FlitAgent → Connect in its wp-admin.
- “[site] is not confirmed: this account already has 50 connected sites. Disconnect one, then connect [site] again from its wp-admin.” An account holds up to 50 sites. Disconnect one under Sites in your account, then connect this site again from FlitAgent → Connect.
Reaching the site
“flitagent.com could not reach [site]” is followed by the reason:
- its address could not be found: the domain does not resolve. Check the site address in Settings → General.
- it points to a private network address or its address is not allowed: flitagent.com reaches only public addresses, so local and private sites cannot be connected.
- the connection failed or timed out after [n] s: the site is down, slow or blocking flitagent.com.
- it answered with HTTP [status]: the host, a firewall or a security plugin answered with an error page.
- it did not answer as FlitAgent: the plugin is inactive, or a cache or firewall answered instead of WordPress.
- its answer was larger than 4 MB: ask for less at once, for example fewer items per page.
For each of these, run Test connection and see Site not reachable.
- “flitagent.com could not sign the request to [site]. Try again later.” and “flitagent.com could not send the request; try again later” The problem is on flitagent.com’s side. Try again later; if it keeps happening, tell us.
- “flitagent.com is busy, try again in a moment” Many calls were in progress at once. Try again.
- “[site] is not accepting requests from flitagent.com. Check FlitAgent → Connect in its wp-admin.” The site refused flitagent.com’s signed requests, usually because it was disconnected in FlitAgent → Connect. Connect it again there.
- “The WordPress user who connected [site] can no longer use FlitAgent there. Connect again from its wp-admin.” That user was deleted or is no longer an administrator. Disconnect the site in FlitAgent → Connect, then connect it again as another administrator.
Tools
- “flitagent.com has not loaded the tools of [site] yet.” Ask the app to list its tools again, then try again.
- “[tool] is not a tool of [site].” and “[tool] is no longer a tool of [site]: its tools have changed.” The site’s tools differ from what the app remembers, for example after a plugin update or a page builder was deactivated. Start a new chat.
- “[tool] is no longer available on [site]: its Access for AI tools is now Read only.” and “[site] refused a write. Writes may be turned off in its FlitAgent settings.” The site allows reading only. An administrator can choose Read and propose changes under FlitAgent → Settings.
- “[tool] cannot be used through flitagent.com: it declares its own site argument.” The site runs an older FlitAgent. Update the plugin.
The app
- “The access token is not valid for this address. Connect the app again.” Remove flitagent.com from the app and add it again.
- “Connect this app to flitagent.com first.” Add flitagent.com to the app: Connect your AI app.
- “The site’s administrator disconnected [app] from this site in wp-admin. They can set it up again under FlitAgent → Connect.” [app] is ChatGPT, Claude or Manual configuration. The site refuses that AI tool’s requests until an administrator sets it up again in FlitAgent → Connect.
Limits
- “You have reached the limit of [n] tool calls a minute for this account.” or a day: wait until the time the message gives. Usage in your account shows your calls.
- “Too many requests for this account. Try again in [n] s.” Wait that long, then try again.
- “The request is larger than 1 MB.” The app sent too much in one call. Ask it to split the work.
Not listed here? Get help.