Direct answer
After a break or uncertain error, list books, load the selected book’s status, start a fresh session, and use the latest chapter packet. For an uncertain write, verify stored state before retrying with the same idempotency key.
Step by step
The reliable workflow
- 1
Reconnect if needed
Complete OAuth again only when the app reports expired, denied, or insufficient access.
- 2
Read status
Confirm the current chapter, accepted count, last mutation, goal, and active packet.
- 3
Reconcile uncertainty
If the expected change already appears, do not repeat it.
- 4
Continue from the newest packet
Discard stale chapter context and resume with the current version.
Offline
Cards display an offline state and do not pretend to refresh. Previously saved server state remains unchanged.
Reconnect
A reconnect request should explain which scope is missing. BookWriter validates token issuer, audience, expiry, and granted scopes on every protected call.
Delayed publication work
Respect retry_after_seconds. A queued render is not a failed finalization and should not consume another unique snapshot.
Frequently asked
Should I create a new book after a loading error?
No. List books and reconcile the existing project first.
Keep going
Continue the connected writing workflow.
Canonical URL: https://www.bookwriter.vip/mcp/guide/resume-and-recover · Updated July 15, 2026