Skip to main content Skip to page footer

Known issues

Known problems and what helps in each case. As of version 0.4.0.

Symptoms and causes

  • The button does not appear at all. The backend group lacks the permission “Enable Chat Interface” (enable_cheddi_interface), or the caches were not cleared after installation. Check both, see Permissions.
  • The input area stays locked and reports a missing API key. No aiSuiteApiKey is stored in the AI Suite. Without it the chat does not accept any request.
  • The chat reports that the key for this model is missing. Your plan runs on your own provider keys, and none is stored for the selected model. Add it in the AI Suite extension configuration under “Bring Your Own Keys” or choose a different model.
  • The model selection is empty. The group lacks the model permissions, or GDPR mode leaves no suitable model.
  • ChEddi claims it has no tools available. Start a new conversation, that resolves it in most cases.
  • The request aborts with “Tool-call limit reached”. The request was too large or too vague. Split it into smaller steps, see Confirming: read, write, delete.
  • Credits used up. The input area locks until the allowance is topped up.
  • An attachment is rejected or not read. Images are not supported yet and are rejected on upload. For documents, the response to the upload names the reason, for instance too large or a format that cannot be read on this installation. Since version 0.3.0 the environment report also shows which formats cannot be read (see Operation). More on formats and limits under Attachments.
  • Web research is unavailable. The chat states the reason at the top: a missing group permission, a missing key on a plan with your own provider keys or, with GDPR mode active, that the server has no EU search provider or that this provider does not serve the language region of your website.
  • Conversations have disappeared. They are deleted automatically after the configured period without activity, 20 days by default. The help window in the chat tells you the value that applies to you, see Operation.
  • Long requests end in an error. Often max_execution_time or a web server or proxy timeout is lower than the 180 seconds a request may need. The environment report warns about this, see Operation.