Resources
Troubleshooting
Fixes for the problems people hit most, by symptom.
Browser calls fail silently#
Open the console: every refusal logs a [tug]warning with the API's message. In the network panel, the response body has the error code and the Request-Id header identifies the call. Codes are explained in Errors.
SDK requests fail with 403#
origin_not_allowed: the project's Allowed origin doesn't match the page making the call. On the project page, under Allowed origin, click Allow any origin while you build, or set it to the exact origin (for example http://localhost:5173).
Preview returns nothing#
- The user ID must match the
distinctIdin your events, and the user must be in a cohort (check the member count under Cohorts). - At least one message must be approved for that surface.
- The user may be held back: in the holdout group, capped (once a week by default), already converted, after a dismissal, or erased.
0 members after intelligence#
Cohort rules need matching events. Send real traffic (or, on a project with no events yet, use Send test events), then run intelligence again. Goals with a target event produce better cohorts.
402 Payment Required#
The trial has ended or this month's allowance is used up; the error code says which. Upgrade on pricing or check usage under Settings, Billing. See Billing.
PostHog webhook returns 401 or 403#
403 webhook_not_enabled: click Enable PostHog forwarding on the project page before PostHog sends traffic.401aboutX-Tug-Webhook-Secret: the header value must match Tug exactly (case-sensitive). Copy it again after rotating.401 invalid_public_key: the webhook URL must include the right?publicKey=phk_live_…from your project page.
PostHog webhook returns 400#
- The body has no
eventanddistinct_id: use the destination body. - Literal
{event.event}strings in the body mean PostHog didn't apply its templating.
The same PostHog event appears twice#
Your destination body is missing "uuid": "{event.uuid}". Add it (copy the destination body) and retries are stored once.
Still stuck?#
Create a fresh project and use Load demo data for a known-good path (the Quick start), then compare your own user ID with the one in Preview decision. If you write to support, include the requestId from the error.