Common BusinessStub issues and first checks.

Approval Link Unavailable

This usually means the URL is missing its token, the token expired, approval already completed, the link came from a different environment, or the link was copied without the password setup token.

1. Use the full link from the latest approval email.
2. Confirm the link came from the same BusinessStub environment being opened.
3. Ask a platform admin to check whether approval is already completed.
4. If the link expired, ask for a new approval or direct invite email.

Billing Page Missing Renewal Date

A missing renewal date is expected when no recurring subscription exists, the agreement had only a one-time charge, the webhook has not recorded the subscription yet, billing sync has not pulled the current period, or the account is not linked to the Stripe customer.

1. Platform admin: run billing sync.
2. Confirm the subscription exists in Stripe.
3. Confirm the BusinessStub account has the expected Stripe customer.
4. For one-time-only approvals, no renewal date is expected.

Unauthorized Admin Action

This usually means the user is not a platform admin, the stub is not assigned to the account, the browser session expired, or the request was blocked because it came from another origin.

1. Sign out and sign back in.
2. Confirm the account role shown in the admin header.
3. Platform admin: confirm the user has access to the stub.
4. Retry from the same BusinessStub origin.

Chatbot Not Saving or Responding

Common causes are disabled chatbot settings, a missing same-origin stub-site proxy, missing or mismatched intake credentials, central AI configuration problems, or rate limiting.

1. Confirm chatbot is enabled on the stub.
2. Confirm the public widget posts to same-origin /api/chatbot.
3. Confirm the server route forwards to BusinessStub with the server-side intake key.
4. Confirm a BusinessStub inquiry appears after a test message.
5. If replies are generic, review bot knowledge and platform AI configuration.

Inquiry Not Appearing

Common causes are a wrong slug, missing or invalid intake key, a form posting somewhere else, an archived or mismatched stub, rate limiting, or an operator account that cannot see older inquiries.

1. Test the public listing form on the BusinessStub listing page.
2. For external sites, confirm the site forwards to BusinessStub through its own server route.
3. Confirm the forwarded slug and intake key match the BusinessStub stub record.
4. Platform admin: check all inquiries, not only the operator's scoped view.

Custom Email or DNS Not Verified

BusinessStub does not currently show DNS verification status in admin. Verify the sender and receiving setup in Resend and DNS tools.

1. Confirm custom email is enabled only after sender setup is complete.
2. Confirm the stored key hint matches the intended Resend key.
3. Verify the sending domain, reply domain, SPF, DKIM, and MX records.
4. If uncertain, disable custom email so BusinessStub can use the platform sender.

Favicon or Image Missing

For favicons, confirm the live site has a reachable favicon and use Fetch favicon from the stub form. Check the favicon URL and last error readouts.

For website editor images, confirm the upload saved a path into the content field and that the deployed stub site serves that path publicly. Push a preview and inspect it before saving live.

Website Editor Unavailable

The Website tab needs editor access enabled, repo settings, schema path, content path, and a readable schema/content file. Preview deploys also need a configured preview hook or supported host integration.

1. Confirm the stub has website editor enabled.
2. Confirm repo owner, repo name, branch, schema path, and content path.
3. Confirm the schema has a top-level fields array.
4. For Worker-backed sites, configure a preview build hook if one-button previews are needed.