Skip to guide content
All guides

Getting started

When your work is interrupted

Checks for loading errors, providers, unsaved drafts and access issues.

On this page
  1. Data will not load
  2. A chapter is waiting or failed
  3. Saving fails or reports a conflict
  4. An action is missing or locked
  5. Include useful details in a support request

Data will not load

Keep your current page open and use Retry in the failed section. If several sections fail, check connectivity and your sign-in session. A failed list does not mean books, keys or members were deleted.

A chapter is waiting or failed

Open chapter details or the queue to distinguish waiting from failure. Check the provider selected in Model settings, not just which providers are connected.

  1. API key provider: check its connection and any authentication or allowance message.
  2. ChatGPT: check that the extension is online and ChatGPT is signed in.
  3. Balance or permission error: read the message and current access in Plans & billing.
  4. After fixing the cause, retry affected chapters instead of resubmitting the entire book.

Saving fails or reports a conflict

For a save failure, keep your edits, check connectivity and retry. A conflict means content or settings changed elsewhere. Record your edits, load the latest version and compare before saving again; avoid overwriting from an outdated copy.

An action is missing or locked

Members and workspace owners can have different permissions. Read the notice, check that you are signed into the right account and ask the manager to check access. For changed plans or allowances, use the current information displayed in the application.

Include useful details in a support request

Record the section, action, time and exact error message. Redact unnecessary email addresses, passwords, API keys, pairing codes and signing secrets from screenshots. Say whether the problem affects one chapter or an entire book.

Open support

Read next

Need more help?

Include the step you were taking and the error message. Never send passwords, API keys or webhook signing secrets.

Open support