Transfer Troubleshooting and Recovery
Identify the failed stage first: select source → connect platform → prepare content → create/upload → inspect destination. This helps avoid repeated uploads for an authorization problem or duplicate creation of a page that already exists.
The platform is missing
Ordinary result transfers and Batch transfer offer Notion and FlowUs. WebDAV and NotebookLM appear in 30-day temporary storage → project menu → Transfer to a third party. Zotero is in the result's Export dialog, outside this four-platform selector.
These workflows require the desktop app and relevant capabilities. Check the entry overview instead of repeatedly looking for desktop-only controls in a browser.
Authorization finished but Configure is still shown
- Keep Doc2X desktop open and check the current Doc2X account.
- Open Account management → Online Save Settings and check whether the service is Authorized or its configuration was saved.
- An external browser's return message only means it attempted to return to desktop; check the desktop status itself.
- If the state did not update, start a new authorization. Do not reuse an old authorization callback link.
- If authorization exists but the provider rejects the action, check account eligibility, page permission and capacity.
Start transfer is disabled or content is missing
Check that the task completed, text loaded and the platform is configured. Project transfers also require a title, destination and file list.
NotebookLM projects need readable parsed content; selecting only the original PDF does not supply a missing parsing result. The ordinary Notion/FlowUs flow also cannot turn a fixed-layout-PDF-only result into a text-page transfer.
Will later translations synchronize automatically?
No continuous synchronization is performed. A transfer uses the content selected at that time; later translations or edits do not update existing pages or backup packages. Inspect the destination and its duplicate-handling behavior before deciding how to update it.
Where is the saved result?
| Destination | Check here |
|---|---|
| Notion / FlowUs | Pages in the authorized space, located by the title you used |
| WebDAV | The project ZIP under the destination's doc2x folder |
| NotebookLM | The selected or newly created notebook's source list |
| Zotero | Notes or PDF attachments under the selected literature item |
Doc2X previews the source parsing/translation result. It is not a preview of the final external page; inspect the actual destination.
Existing, skipped and repeated transfers
Notion/FlowUs check prior transfer records and may skip processed results. Find the earlier page before deleting source records or repeatedly submitting the entire batch.
WebDAV creates project ZIPs; using the same destination name may overwrite a package. Use distinct titles for version retention and inspect what the drive actually saved. Check existing NotebookLM sources before retrying to avoid unnecessary duplicate imports.
Partial success and image failures
- Page created, only some content added: inspect the text, tables and images in the service and keep the error stage/message. Repeating the whole transfer may create duplicates.
- Attachment preparation failed before page creation: restore source image/file access, then retry.
- Project packaging failed: identify the unavailable PDF, translation or image before backing up again. A valid connection does not prove a complete package.
- Some batch items failed: use item states to select only what needs attention and retain successful results.
Accounts, disconnection and retention
Connections are bound to the Doc2X account. Switching accounts during a transfer can interrupt or invalidate it. Return to the original account and recheck the destination before continuing.
Revoking authorization or removing a WebDAV configuration manages the local connection; it does not clean up all historical content in the external service. Use local archives or separate backups for originals. Third-party content pages do not guarantee preservation of original file formats, folders or bytes.
Contacting support
Use Contact and include the desktop version, destination service, single/batch/project entry, failure stage, whether content already exists at the destination, and a redacted error screenshot. Do not send passwords, app passwords, authorization codes or tokens.