ManYue downloads: manage the queue, retry failures and verify local copies

English translation of the Chinese original, translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained.

Download management answers three questions: what is transferring, what has finished, and what needs attention. It is not another cover browser for the remote library. After queuing tasks, check the results and open local copies. In a batch, one successful task does not establish that everything is available offline.

Prepare a small, controlled batch

Choose a comic or chapter explicitly supported for download by the current source and confirm access permission. Check space and connectivity first so prolonged offline status, server sleep, or expired credentials are not mistaken for a queue problem. Start with one to three items, then expand once you understand the state changes.

Define the intended scope, such as one complete file or chapters two and three. Sources may create tasks at different granularities; matching titles do not imply identical saved content. Some concurrency and batch options require membership. Use the options visible to your account rather than copying someone else's concurrency count.

Find the task and read its status

Open Download Management and inspect Downloading, Completed, Failed, and similar categories. Verify the task name and source, then watch status and progress. Successful addition means the task entered management; transfer, processing, and import may not all be finished.

For tasks showing size or progress, note a time and watch whether the value continues changing. Do not repeatedly add the same content while it is progressing normally. Duplicate tasks make it harder to identify the final copy. With many tasks, organize your checks by status rather than clicking randomly through a long list.

Pause and resume as needed

Before switching networks or yielding resources to other work, check whether the task offers Pause. Confirm the paused state before proceeding, and confirm that it resumes working afterward. Do not assume every source and processing stage has the same resumability; follow the operations offered by that task.

More concurrency is not always better. A personal NAS, mobile network, or server account may impose limits. If one task is stable but several fail repeatedly, reduce the simultaneous count and observe. The goal is verified completed content, not a busy-looking queue. A temporary adjustment is not a universal performance rule for every server.

Diagnose before retrying

In the failed category, record the item and source state at failure. Confirm that the server or file is still accessible before retrying. A changed password or moved remote path will not be fixed by repeated retries; correct the connection or path first, then return to the task.

If only a few items in a batch fail, retain completed items and address only the failures. Repeatedly adding the same task can confuse records; use its existing Retry control first. If failure occurs during processing after downloading, check format and free space as well as network speed. Record the smallest reproducible case for feedback.

Example: one failed download out of three

Suppose you add three of your own comic files. A and B finish; C fails. Open A and B locally to confirm readability, then check that C still exists on the server, the account can access it, and its size is plausible. Resolve the identified problem, retry only C, and record whether it completes.

If C still fails, compare it with another small file from the same source. If that succeeds, investigate C's format or contents. If all files fail, return to connection and permission checks. This comparison does not require deleting A and B or clearing the whole library to solve one task.

Read how files are handled before clearing tasks

Deletion prompts may distinguish deleting a task from deleting the task and its files. Read the current dialog and decide whether you are organizing records or freeing storage. Do not assume Clear Completed always frees all comic storage, or that deleting a record always retains every related file.

Completion means a successful task state, locally accessible content, and readable beginning, middle, and end pages. Test without a connection when preparing for offline use. A completion record is a clue; the actual reading copy determines whether you can continue. Do not bulk-clear completed tasks and files before retaining the content you need.

Why is a completed item missing from my bookshelf?

Check Local Comics and the destination group, then verify the task's scope and source. Group membership and local-content records may be different layers, so do not search only one custom group. Confirm processing completion before immediately downloading again.

It is still slow after increasing concurrency. Should I keep raising it?

No. The bottleneck may be the source, network, file processing, or device storage. Establish a stable single-task baseline, then adjust gradually. Reducing variables after a failure produces more reliable results than repeatedly trying maximum concurrency.

Sources and version

Checked on October 22, 2026: ManYue 2.0.2 for iPhone / iPad. Based on the public description on the China App Store, Apple release lookup and the corresponding feature entry points. Interface labels may change with the version. Feature access is determined by the app’s current purchase screen.