Direct answer
A failed production sync leaves the previously published version intact. GitBook does not partially update the live space when the push is rejected; the existing commit reference stays active until a successful sync replaces it.
Likely explanation versus confirmed facts
Likely explanation: The connected GitHub or GitLab account can read the repository for local preview, but the GitBook integration lacks write access to the synced branch, or the workspace plan does not authorize automated production publishing.
Confirmed facts:
- Local markdown preview validates rendering on your machine; it does not confirm repository write permissions or GitBook plan-level sync authorization.
- Git push semantics are atomic: if the remote rejects the push, no remote branch reference moves and no new content becomes live.
Steps for this case
- Open the GitBook space, go to Settings → Git Sync, and note the "Last successful sync" timestamp and any error badge.
- Trigger a manual sync and read the detailed error modal. Look for words such as "permission," "plan," or "fork out of sync."
- Confirm the connected service account has push rights on the branch GitBook syncs to, commonly main or master. Run this read-only check:
git ls-remote --heads origin- If the branch appears but your account cannot push, update the integration token or repository permissions.
- If the error references a plan limit, upgrade the workspace or contact GitBook support; lower-tier plans may restrict sync to import-only mode.
Assumptions and uncertainty
I assume GitBook applies standard atomic Git push behavior. The claim that GitBook retains live content on failure is based on product behavior descriptions, not independently verified source evidence, so treat it as likely rather than guaranteed. Transient network errors or cached auth tokens can also produce generic "sync failed" messages that resolve without plan changes.
Missing diagnostic detail
Does the sync error modal mention a plan limit or a permission denial? This determines whether you should adjust repository permissions or change your GitBook plan.
gitbook