# ManYue after a server rescan: verify changed chapters and old bookmarks

Language: en
Canonical: [ManYue after a server rescan: verify changed chapters and old bookmarks](<https://allluckly.cn/en/guides/manyue-server-rescan-identity/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-server-rescan-identity/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-server-rescan-identity/>)
Published: 2026-10-26T00:00:00+08:00
Modified: 2026-10-26T11:37:28+08:00
Author: Bison

Compare chapters and artwork after server renaming, additions or file replacement, distinguishing server scans, metadata refreshes and app catalogue updates.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-server-rescan-identity/>), translated on 2026-10-26. Original publication dates, attribution, code and version notes are retained.

After a server reorganises and rescans files, the app may show new chapters, old names or apparent duplicates. Establish what changed on the server before comparing catalogue entries and actual pages. The key question is whether existing reading references still point to the intended content.

## Record the catalogue and position before maintenance

Before planned maintenance, record the chapter list, active volume, reading scene and important bookmarks. Separate adding books, renaming, artwork changes and content replacement where practical. Keep credentials out of shared captures. If records are reconstructed afterwards, label uncertainty. A usable before-state is necessary to explain what a scan changed.

## Verify the server’s own result first

Use the intended reader account to verify the server’s resulting catalogue and pages. Server scans, analysis and metadata refreshes can serve different purposes; Komga documents them separately. Follow your server’s instructions and wait for the relevant job to finish. If the server itself lacks a new volume, refreshing the client repeatedly cannot create it.

## Refresh the app catalogue and compare changes

Refresh or reload through the connection’s available controls and compare title, chapter list and cover separately. Cached artwork can lag behind readable new chapters, and a title change does not establish content replacement. Use ordinary re-entry if no explicit refresh control exists. Avoid deleting the whole connection at the start, which changes several comparison conditions at once.

## Open the actual added or replaced pages

Inspect early, middle and final pages in a new chapter and an existing one. For a same-name file replacement, verify a scene known to have changed rather than relying on the filename. Artwork and story changes can require different server handling. Identify the stale layer before making client-side edits that could obscure the server’s actual mapping.

## Verify old bookmarks against the story

Open important old bookmarks and compare chapter, scene and neighbouring pages. Added covers, changed spreads or file replacements can shift the content while leaving a numeric reference intact. Find the original scene in the current file before creating a new reference. Keep the old one until checking is complete and recognise old-identity history entries as such.

## Compare downloads with the server edition

A downloaded copy can remain the pre-maintenance edition. Verify its representative pages and coverage independently. Decide whether to retain it or obtain the updated file, preserving references and availability before replacing anything. Label the local edition in the maintenance record so later differences are not mistaken for random sync faults.

## Report the stale layer precisely

Report the server web view, app catalogue, actual page result and downloaded edition separately. One stale layer narrows the investigation; all-old results call for checking whether maintenance completed and the account reaches the intended library. Include item identity, maintenance type and time. Avoid combining scans, cache wipes, connection deletion and full reimports into one opaque attempt.

## Questions and completion criteria

Why can bookmarks shift after a catalogue refresh? Updating names does not reinterpret changed page structures. Do server replacements automatically update offline copies? Verify rather than assume. Finish with matching server and client catalogues, correct changed pages, checked important bookmarks and clearly identified local editions. Keep the before-and-after record for later maintenance.

## Related guides and sources

[Connect ManYue to Komga: permissions, series, books and offline checks](<https://allluckly.cn/en/guides/manyue-komga-library/>); [ManYue bookmarks and notes: save a page and return to the right place](<https://allluckly.cn/en/guides/manyue-page-bookmarks/>).

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and [Apple public version lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn>). This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.

For server maintenance, also consult the [official Komga scanning, analysis and metadata-refresh documentation](<https://komga.org/docs/guides/scan-analysis-refresh/>), using the instructions appropriate to your server version.