Skip to content
FORMO.
On this page

TroubleshootingUpdated 12 Aug 2026

Common errors and what they mean

Widget, origin, Shopify, and AI failures — visitor copy stays calm; detail stays in the dashboard.

Visitors never see raw provider or Shopify errors. Use Activity and the AI / Integrations cards.

Widget does not appear#

  1. Confirm the script is on the published page (view source, search widget.js).
  2. Confirm the page host is in Setup → allowed domains (www vs apex).
  3. Wait 60 seconds and refresh Setup for Connected.
  4. Check the browser console for a blocked script (CSP). Add your Formo origin to script-src if the store sets a strict policy.

Widget appears, then does nothing#

SymptomCauseFix
Contact form instead of chatSite paused, or monthly cap hitTurn Live on, or wait until the 1st (UTC)
Dry-run notice on every replyDry Run is onExpected until you switch it off in Behaviour
“Chat is almost ready”No AI key savedDashboard → AI Provider
Origin not allowed (403 on config)Script copied onto another domainAdd that host, or remove the tag

Shopify#

SymptomFix
Token test failsDomain must be store.myshopify.com; token must include read_orders and read_customers; reinstall the custom app
Order not foundConfirm the order exists and the number matches Shopify’s name (#1042)
Invented trackingShould not happen — if Activity shows no tool evidence, keep Dry Run on and check the model supports tools

AI provider#

SymptomFix
Key rejectedRe-copy the key; enable billing
Model not foundUse the catalog default or a current custom id
Tools warningPick a tool-capable model so order lookup works
TimeoutRetry; switch to the fast model for the verifier

Rate limits#

Formo limits 20 messages/minute per visitor, 300/minute per site, and 40 new conversations/hour per visitor. Visitors see a short wait message, not an error code.