Troubleshooting

Start in Flarepipe Chat > Settings and press Run diagnostics. It checks the Worker and its bindings and will usually point straight at the problem.

The widget does not appear

1. Check the widget is enabled in settings.
2. Confirm setup actually completed. If the menu item still opens the wizard, it did not.
3. Look for a caching or optimisation plugin that is stripping or deferring the script, and clear the cache.
4. Open the browser console. If the widget's script is not loading, that is a front-end issue on your site rather than a Cloudflare one.
5. Check the corner it is configured for. Another floating element may be sitting on top of it, particularly on mobile.

The widget appears but every message fails

Almost always one of two things:

The origin no longer matches

The Worker only accepts requests from the site URL it was configured with. If you have changed domain, moved from staging to production, or switched between www and bare, the Worker is refusing the requests. Re-save the settings to redeploy it with the current origin.

The model is gone

If Cloudflare has retired the model you are using, requests fail once the fallback is exhausted too. Check for an admin notice from the health check, then set a current model identifier as described in models.

Content is not being indexed

1. Check WP-Cron. Indexing runs in background batches. On a low-traffic site WP-Cron may not fire on its own. This is the most common cause by a wide margin.
2. Check the post type is selected in settings, and that the content is actually published.
3. Check the exclude box in the editor sidebar for the specific item.
4. Use "Sync content now" to force a pass.

The bot gives wrong answers

Work through these in order: the first is by far the most common and the last is the least.

1. Outdated content is being cited. Ask the bot for its source, then look at that page. If it is genuinely published but no longer true, tick the exclude box or update it. Most "the bot lied" reports are the bot faithfully reporting something you forgot you had published.
2. Nothing covers the question. Write a Chat Knowledge entry with the right answer, phrased the way visitors ask it.
3. A fact needs to be always-on. If it must never be missed, put it in the site facts box rather than relying on retrieval to surface it.
4. The model is the problem. Only after the above, try a different answering model.

The bot says it does not know things it should

The bot only answers from passages that clear a confidence threshold, so a "I do not know" usually means retrieval did not find a close enough match rather than that the content is missing.

• Confirm the content is actually indexed by asking something quoting its exact wording.
• Consider phrasing. Content written in your internal vocabulary will not match a visitor's words. A knowledge entry that asks the question in the visitor's language and answers it in yours bridges that gap.
• Very short pages produce weak chunks. A one-line page rarely retrieves well.

Answers stop mid-sentence

A known beta limitation: no explicit length limit is passed to the model, so long answers can be cut off. Steering the bot toward shorter answers in your site facts helps in the meantime.

Answers contain asterisks or pipe characters

The widget renders a deliberately narrow subset of Markdown and does not convert lists or tables, so their syntax shows through. Asking for prose rather than lists in your site facts is the current workaround.

Visitors report being rate limited

The limit is 20 messages per minute per IP. Genuine visitors rarely reach it, but people behind a shared office or campus IP can. The limit is fixed in this release.

The health check keeps failing

The daily check raises an admin notice when the Worker or a binding is unreachable. Run diagnostics for the detail. If the Worker itself has been deleted from your Cloudflare account, create a fresh setup token and run the wizard again. It repairs rather than duplicates.

Setup fails partway

• Token permission errors: compare against the list in Cloudflare setup. A missing Workers AI Edit is the usual one, since Read looks sufficient but is not.
• No workers.dev subdomain: some accounts have never registered one and it cannot always be claimed automatically. Register it in the Cloudflare dashboard, then re-run setup.
• Custom domain refused: the zone must be on the same Cloudflare account and there must be no existing DNS record for that exact hostname.
• Certificate warnings after attaching a domain: issuance can lag a few minutes. Wait before assuming it failed.

Starting over

Start over in settings resets the plugin's local state so you can run the wizard fresh. It does not delete anything from Cloudflare, so remove those resources from the Cloudflare dashboard yourself if that is what you want.

Still stuck

Get in touch through support. Run diagnostics first and include what it says, along with your plugin version and whether you are on workers.dev or a custom domain.