Skip to content
Install the messenger

Fix a widget that is missing or loads twice

Diagnose the actual published website before repeatedly changing the agent.

CCorthex product guidesUpdated October 23, 20263 min read
Where to find itYour public website → browser developer tools
In this article

Before you begin

Activate the agent and open its integration/embed controls. You need permission to add the snippet to your website or configure the relevant plugin.

Example workspace · Demo data. Copy the snippet belonging to your agent. Replace example identifiers before use. Select the image to enlarge it.
Embed snippet for an example agent

Example workspace · Demo data. Copy the snippet belonging to your agent. Replace example identifiers before use. Select the image to enlarge it.

Step by step

  1. 1

    Check the published page

    Open the real URL outside the site editor. Confirm the Corthex script is present once and references the intended bot ID.

  2. 2

    Check loading

    Inspect the browser network/console for blocked script or iframe requests. Compare a clean browser profile without extensions.

  3. 3

    Check activation and mode

    Confirm the agent is active and that inline/custom launcher settings are not hiding a standard floating button.

  4. 4

    Remove duplicate installations

    Check the shared template, page-specific scripts, tag manager and CMS plugin. Keep one deliberate installation.

  5. 5

    Retest safely

    Reload a fresh visitor context on desktop and mobile. Keep a record of the exact failing URL and error if you need support.

Solve the most common setup problems.

  • The bot gives weak or invented answers. Confirm the source is ready, remove conflicting/old material, add the missing policy as knowledge and test the exact question again. Narrow the operating instructions so the assistant knows to say when evidence is unavailable.
  • The widget does not show. Verify that the script is published on the page, its data-bot-id is the correct UUID, and the bot is active. Check the browser console for the missing bot-id message and make sure content-security rules permit the widget’s host.
  • The bot is silent in a conversation. Check whether staff has taken over the conversation. A staff-owned chat returns a 423 response to the developer API and waits until someone resumes the bot.
  • A source is not usable yet. Wait for processing to complete. If it fails, check file type/size, URL reachability or feed validity, then retry with cleaner text or a smaller source.
  • An API request returns 401 or 404. For 401, verify the Authorization header has the Bearer prefix and an active API key. For 404, check the bot UUID, its active state and that it belongs to the key’s organisation.
  • The assistant is still paused after staff support. Open the session in Staff Console and select Resume. Takeover is intentionally persistent to prevent conflicting human and AI replies.

Good to know

Your site’s security policy can block the script or frame. Adjust only the required documented origins; do not broadly disable browser security.

Check the result

Publish the website change, open the public page, send a test question and verify the correct conversation appears in the correct Corthex workspace.

Questions & troubleshooting

It works for me but not a visitor

Compare consent settings, extensions, published templates, browser version and the exact URL.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.