KB not publishing

Overview

This guide helps you fix issues that prevent your public knowledge base from showing updates. Common causes include pending approvals in the review inbox, unpublished drafts, a disconnected or failing PR to your target repository, or domain setup problems on your tenant subdomain or custom domain.

Follow the sections below to find and resolve the specific blocker so your pages appear at your public site.

Before you start

• You can sign in to your Moxie Docs workspace.
• You have permission to access Dashboard → Knowledge base setup and the review inbox.
• Your GitHub account is linked to the target repository used for publishing.

Pages are stuck waiting for approval

You see new KB‑specific drafts in the review inbox, and nothing appears on the public site. This happens when pages need a human review before they can be committed and published.

1. Open Dashboard → Knowledge base setup.
2. Click Review inbox to see pending drafts.
   • Drafts show their status and the target repository.
3. Select a draft and click Approve to publish, or click Request changes to send it back.
4. Wait for the approval to create a docs‑only PR in your target repository.
5. Confirm the PR is merged (see next section if it isn’t), then refresh your public site.

Pull request did not merge to the target repository

You approved a draft, but the change is not live. Moxie Docs opens a docs‑only PR to your target repository; if the PR is blocked, the page will not publish.

1. Open the approved item in Dashboard → Knowledge base setup → Review inbox and click View PR.
2. Review the PR in GitHub for required checks.
   • Required reviews: Have a maintainer approve.
   • Failing checks: Fix or disable required checks, then re‑run.
   • Merge conflicts: Resolve in GitHub and click Merge.
3. Merge the PR in GitHub.
4. Return to your public site and refresh to see the update.

Drafts exist but were not generated

You expect new pages but see nothing in the review inbox. This can happen if the repository is not connected or no recent changes triggered generation.

1. Open Dashboard → Knowledge base setup.
2. Check that the correct repository is listed as the target repository.
   • If it’s missing, click Connect repository and follow the prompts to link GitHub.
3. Confirm recent changes exist in the repository that should produce KB drafts.
4. Click Generate drafts (if shown) or wait for the next sync to create new items in the review inbox.

Public site shows a 404 or still shows an old version

Your pages are approved and merged, but the public site at your tenant subdomain does not update.

1. Visit Dashboard → Knowledge base setup and check Site status.
   • If status shows Deployed with timestamp, proceed to refresh the page.
2. Open your public site at your *.moxiedocs.app address and hard refresh the page.
3. Try the direct page URL from the review inbox confirmation and verify it loads.
4. Wait a few minutes and refresh again; propagation may take a short time after merge.

Custom domain is not working

You use a custom domain, but the site does not load or redirects to the tenant subdomain. This usually means domain setup is incomplete.

1. Open Dashboard → Knowledge base setup → Domain.
2. Verify the custom domain is added and shows Connected.
   • If it shows Action required, follow the on‑screen DNS instructions.
3. Update your DNS with the exact records shown in Domain.
4. Wait for DNS to propagate, then click Verify in Domain and reload your site.

Search results show removed or outdated pages

You changed or deleted pages, but the public site search still shows the old version.

1. Confirm the change was approved and the PR merged to the target repository.
2. Open the public site and refresh the page.
3. Use the site search again; indexing updates shortly after deployment.
4. If still outdated after some time, reopen the page draft in the review inbox and resave to trigger a fresh index.

Still need help

• Recheck: the review inbox for pending approvals, the target repository PR status, and the Domain page for connection or DNS issues.
• If you lack access to Dashboard → Knowledge base setup, contact your workspace admin to grant permissions or complete domain setup.
• If problems persist after approvals are merged and the site shows Deployed, contact your workspace admin to review repository settings and required checks in GitHub.