Book Isle single-item import retry: retain successes and verify one sample

When a batch partly succeeds, handling one failure need not mean importing everything again. Book Isle 1.1.4 publicly improves single-item retry and handling messages. Use an existing failure to check one sample while retaining originals and successful books. Verify results in the bookshelf; this article neither manufactures damaged files nor claims retry resolves every failure.

Record the batch and successful items first

Choose an authorised batch that actually contains a failure and record import date, source, filenames, successful items and target failure. Without failures, do not damage files for practice. Open one successful book and record title, edition and a body-text anchor as the baseline. Retain source books separately rather than using the failure list as the sole inventory. Handle one target without deleting successes, clearing the bookshelf or rebuilding a database to tidy counts. Batch identity distinguishes old successes from later processing results.

Identify the target in the import queue

Open Import Queue in the installed version’s settings, or an actual Failed Imports entry on the bookshelf. Match title, source, record time and error, not name alone. Record the displayed category, such as local or shared import, because sources differ. Note any active filter rather than treating fewer visible rows as disappearance. Inspect the target row before acting; the top Retry All Eligible Items action is not single-item retry. If absent, check batch and entry instead of reimporting everything to manufacture a visible failure.

Check whether the source remains available

Through a trusted existing file entry, confirm the original exists, is readable and is not merely a cloud placeholder; obtain a complete copy where needed. Check actual format rather than renaming an extension as conversion. External readability establishes this file’s availability, not continued access through the failure record’s stored source. For moved files, missing shared material or manual-handling messages, preserve the record and follow instructions to reselect or reshare the original. Do not alter private paths, replace internal queue files or delete other books to produce a retry button.

Retry only one eligible target

Open the row’s action sheet, verify title and error, and use Retry This Item only when actually offered. Follow manual-handling instructions instead of searching for hidden controls when it is absent. Wait for the operation to finish without repeated taps or simultaneous full-batch reimport. Record target identity, time and action before retrying. Single-item scope defines the request, not repair of its underlying cause. Availability, format problems or repeated failures may still need attention; an enabled button does not guarantee success.

Classify the message instead of only counting fewer rows

Keep the actual processed, requeued or still-failed result and identify this single-item attempt. Requeueing means later processing, not a readable book. Processed can include recognising an existing copy and resolving an old failure record, not necessarily adding a book. Verify a disappeared row in the bookshelf rather than defining completion by a lower failure count. For persistent failure, retain the new error and time and compare changes instead of repeated retries that obscure the original cause. The next status guide covers these distinct follow-ups.

Verify content and retain prior successes

Open the target and check name, format/readable-edition identity, opening text and one later passage, excluding a namesake or empty entry. If a readable copy already existed, identify the one actually used rather than importing again to increase counts. Reopen the successful baseline book and confirm its anchor and that your actions did not accidentally change its records. This verifies selected samples, not every page in the batch. Investigate duplicates through source and content; cleanup is separate, with no default deletion of originals during retry.

Leave and return to verify the state

Leave both queue and reader, return through the original entry and inspect whether the target remains failed, is pending or is readable in the bookshelf. Separate queue outcome from content outcome with version, source and time; an initial message is not permanent state. Shared work may start later or fail again, so inspect the current result. Mark waiting or unverified where necessary rather than clearing evidence to look resolved. Keep successes and originals recoverable and report a nonprivate original sample instead of a book or private path.

Finish one bounded single-item retry

Completion means acting only on the identified target, preserving the message, checking content and confirming previous successes remain usable. A removed failure can mean queueing or existing-copy resolution, and an externally valid file does not restore a lost source path or retained copy. Follow displayed handling instructions instead of assuming automatic retry for every source. Record actual success, continuing failure or pending work with required files/information. Clearing a list is not resolving a problem, and this workflow is not a claimed physical-device test.

Related guides and sources

Book Isle batch import: move an old collection with a clear audit trail; Book Isle import states: distinguish requeued, processed and manual handling.

Checked on November 6, 2026: Apple public version information lists Book Isle 1.1.4, requiring iOS / iPadOS 15.6 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.