Troubleshooting

Most issues fall into one of four buckets. Find yours below; if it's still stuck, email support@starkspherelabs.com with the page URL.

Friday doesn't load

Symptom: you installed the script but no launcher appears.

1. Open DevTools → Console. If you see a CSP violation mentioning script-src or connect-src, your site's Content Security Policy is blocking Friday. Add friday.starkspherelabs.com to script-src and connect-src.
2. DevTools → Network: filter for widget.js. If it's missing, the script tag isn't reaching the rendered HTML — check your theme's footer hook (WordPress) or the snippet placement (other sites).
3. If widget.js returns 200 but no launcher appears, check the console for a "data-key invalid" or "host not allowed" error. The key in your snippet may not match a workspace, or your host isn't in the workspace's allowed-hosts list.
4. Sealed shadow DOM? Some site builders wrap your page in a closed shadow root. Friday can't penetrate it. Move the script outside the shadow, or use the extension.

Friday picks the wrong action

Symptom: visitor asks for the pricing page, Friday opens the FAQ. Or visitor says "book demo" and Friday tries to fill the newsletter form.

• Add a vocabulary entry pinning the phrase to the correct target. Vocabulary beats fuzzy matching.
• Add data-friday-id to the right element so the scanner has a stable, unambiguous selector for it. See Scanner.
• Hide misleading lookalikes with data-friday-deny. (E.g. a "Subscribe" link in the footer that gets picked up when the visitor asks for "sign up.")
• Check your action policy for an over-broad Allow rule that's nudging Friday toward the wrong page.

Action doesn't fire

Symptom: Friday says "Done!" but nothing happened on the page.

• React-controlled inputs. Some React apps ignore direct value assignment. The runtime dispatches input and change events to handle this, but a few setups need a synthetic keydown too. If you're seeing this, add data-friday-id and let us know — we'll add a workaround.
• Click swallowed by a wrapper. If the actual clickable element is a deeply nested span and the visible button is an ancestor, the dispatched click event may not bubble correctly. Add data-friday-id to the right node.
• Element re-rendered between scan and execute. If your page renders the action target after the scan but before execute, the selector can go stale. The runtime fails fast and logs to the audit log. Usually fixed by stabilizing your selectors (data-friday-id).
• Synthetic event quirks on custom inputs. If you have a custom date picker / combobox that doesn't respond to standard events, contact us — we'll add a per-domain shim.

<!-- Pin a stable selector so the runtime always finds it -->
<button data-friday-id="checkout">Checkout</button>

Workspace data confusion

Symptom: you can't find a visitor in the dashboard, or "stats look wrong."

• Per-domain workspaces. If you run Friday on three sites and each has its own workspace, that visitor only exists in the workspace whose host they chatted on. Switch workspace at the top of the dashboard.
• Chrome extension workspaces. The extension creates a separate workspace per domain. Visitors from amazon.com via the extension are in the amazon.com workspace, not your main one.
• Embedded vs extension on the same domain. They're different workspaces. They don't share visitor data.

Still stuck?

Email support@starkspherelabs.com with: the page URL, your workspace key, a screenshot of the DevTools Console, and what you expected to happen. We usually reply within a day.