Skip to content

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

Resolve answer and installation problems

Move from a symptom to a safe correction and verify it with a repeat test.

Open copy menu
View as Markdown

Identify the symptom first. Make one change at a time and repeat the same test so you know what corrected the problem.

The agent answers incorrectly or cannot find information

Section titled “The agent answers incorrectly or cannot find information”
  1. Open Data sources and check that the source contains an answer.
  2. Ensure another source does not provide conflicting or outdated information.
  3. Check the source status and the latest knowledge update result.
  4. Correct the content and select Update knowledge base. Wait for completion.
  5. Repeat the original question and try one alternative wording.

If the information is present but the answer does not improve, also check the agent’s Instructions. An overly restrictive or conflicting instruction can prevent a useful answer. Do not remove security boundaries just to pass one test.

The data sources guide explains how to inspect content.

Check the published website, not just a preview in its site editor. Open it in a private browser window.

  • Confirm the installation code appears once in the published page.
  • Check that the code belongs to the correct agent and that the agent is active.
  • Review domain restrictions in Settings → Security.
  • If the browser shows an error or the site blocks an external script, ask the site maintainer to check installation.

Do not remove the site’s security policies entirely. Use the publishing guide to verify the correct setup.

Check your connection and the visible error. If the message offers a retry, use it after connectivity returns. If asked to wait, wait before trying again. Also check usage limits .

If the agent started an external action, confirm its result in the destination system before repeating the entire request. A conversation error alone does not prove that the action did not happen.

Repeat the failing task on the same page and device. Then try an ordinary use case to confirm that the correction did not break something else.

If the problem persists, contact us . Include the workspace and agent, time, browser, expected result and exact error. Hide personal data and secrets in screenshots.