---
title: "Widget troubleshooting"
url: "/help/buuk/widget-troubleshooting"
updated: "2026-11-13T13:32:08.079Z"
---
# Widget troubleshooting

Most widget problems trace back to setup, origins, or the monthly AI allowance. Keep the affected page open in one tab and **Settings → Help widget** in another, and work through the problem below.

**The script is not loading**

Check the **Enable widget** switch first — a disabled widget loads nothing, and its direct chat link stops resolving entirely. Then confirm the snippet carries the public key shown in Settings; a rotated key invalidates every old snippet at once. The widget script is cached for roughly a minute on the browser side, so wait out a 60-second window after changing settings or deploying before judging a fix.

**Requests are rejected because of the origin**

In production, each widget API call is checked against **Allowed origins**. A mismatch answers 401 or 403 with an error body such as `{"error":"origin_not_allowed"}`, or `"origins_not_configured"` when the list is empty.

The symptom in the interface is quiet: the widget opens, but Home, search, and news come back empty. Find the blocked call in the browser’s Network tab — the failed request shows the Origin the page sent — add that scheme-and-host to Allowed origins, and retest.

**Ask AI says answers are paused**

The workspace has spent its monthly AI conversation allowance. Ask inputs say so directly, readers can still browse every article and send their question to your team, and the allowance resets on the first day of the month. See [Plans and billing](./plans-and-billing) — nothing else about the widget changes when it pauses.

**Voice is on but says nothing**

Browsers refuse to play audio before the reader interacts with the page, so voice never auto-starts from a cold load. Press the **Listen** button on a message to start; typing a new question stops audio mid-playback on purpose. Verify **Voice replies** is on and use the **Preview** button in Settings. A preview that fails with an error toast means the request itself could not produce audio — reconfirm the voice toggle before anything else.

**Announcements are not showing**

1. **Show product updates **must be on in Settings → Help widget.
2. Entries must be published changelog releases with **Announce in widget** enabled on each one.
3. Entries targeted at specific reader groups stay hidden from readers outside those groups.
4. Only the five most recent announced entries are kept for the widget; older notes rotate off.

Still nothing? See [Changelog](./changelog) for how per-entry announce works.

**Rotate or disable a key**

The public key ships in client code, so treat leaks as a when, not an if. Press **Rotate key** in Settings → Help widget: a new key is issued immediately and every embed still using the old one stops answering until you paste the new snippet. To silence everything without touching deployed code, flip **Enable widget** off — the embed goes quiet on every origin and comes back exactly where it was.

> [!NOTE]
> The public key alone opens nothing. The combination of the key and an allowed origin is what makes the widget answer — which is why rotation and the origins list are the two controls that matter here.

## Related

- The settings this page refers to: [Widget settings](./widget-settings).
- Install and update steps: [Embed the help widget](./embed-the-help-widget).
- Planning around the allowance: [Plans and billing](./plans-and-billing).
- What readers normally experience: [What the widget can do](./widget-features).