Source: https://restorebunny.com/guides/recover-partial-restoration-batch-before-paying/

# Recover a Partial Restoration Batch Before Paying Again

Reconcile successful, failed and visually rejected batch items before buying again. Keep accepted downloads and retry only justified exceptions.

Family photo projects4 min readUpdated 11 October 2026

## Try it on your own photo

Repair a copy of your photo, then compare faces and details with the original.

[Restore my photo](<https://restorebunny.com/signup/?from=seo-content&source=%2Fguides%2Frecover-partial-restoration-batch-before-paying%2F>)1 credit per successful photo · Account required[See credit packs](<https://restorebunny.com/pricing/>)

Quick answer

## The short version

Reconcile each photo's status, saved output and credit treatment before restarting a partial batch. Keep successful downloads, distinguish technical failures from visually rejected results and resubmit only the unresolved scope when appropriate. An incomplete ZIP or missing preview is not proof that the entire batch should be generated again.

## Define this purchase decision

A batch can contain several different outcomes: successful and accepted, successful but visually rejected, technically failed, or not yet resolved. These labels have different implications for another purchase. Start with the source inventory and recorded job statuses rather than a single impression that the album did not work.

The supported workflow provides per-photo progress and saved results, with a ZIP at completion. Availability can still require troubleshooting. Reload and inspect existing results before creating replacement jobs. Reprocessing accepted files can consume additional credits and deliver a different generated image, so retain what has already succeeded.

## Worked decision example

Worked example: ten selected files produce seven successful outputs, two reported technical failures and one unresolved job. Six of the seven completed outputs are accepted and one is visually rejected. The ledger has six accepted unique photos, seven completed successful attempts, two failure checks and one status check. It does not yet justify buying ten more attempts.

If the two failures are later retried successfully and the unresolved job also succeeds, the first-pass collection has ten successful outputs, including the visually rejected one. A separate rerun for that rejected image would be another successful attempt if it completes. Actual balance changes must follow recorded settlement; these counts explain the categories without pretending to observe a live account.

## Complete the decision worksheet

- Save accepted outputs immediately and match them to source IDs. Do not discard them while investigating missing files.
- Read each unresolved job status and wait for a final state where necessary. Avoid duplicate submission while a job may still be active.
- Compare the balance with successful attempts and recorded failure treatment. Keep job IDs and timestamps for a support request if reconciliation differs.
- Choose a retry list containing only justified exceptions. Recheck compatible settings, intended format and displayed credits before starting that list.

## Resolve the buyer objections

Technical failure settlement automatically returns the reserved restoration credit for a failed output; it is not a discretionary cash refund of the pack purchase. A batch retains credits for its successful outputs and releases the failed-output portion through settlement. Check final status and balance if the release is not yet reflected, then contact support about an unexplained discrepancy. Separate support adjustments may be discretionary, but ordinary failed-output settlement should not be described that way.

Does a poor-looking completed image belong with failed jobs? Keep it separate. It can be technically successful and credit-using even when it fails your own quality review. Include the changed region in a support report where relevant, but do not assume an automatic visual-satisfaction refund.

## Keep a useful decision record

Do not infer success or failure solely from the number of items in a ZIP. Match each file to a source and inspect the recorded job state for items that are absent. A technical status may settle after an earlier screen message, so preserve the final reconciliation rather than comparing against a remembered intermediate balance. If support needs details, supply identifiers and the relevant observed discrepancy through the authorised channel; do not expose private photo URLs in public notes. Once the exception list is stable, decide whether each remaining source merits another attempt. A successful recovery ends with accepted saved files and a clear unresolved list, not merely with the original batch count appearing again.

## Choose the next action

Open the existing album first, reconcile the saved files and statuses, then check your balance. Buy more credits only if the bounded retry scope exceeds that balance and the retry has a clear reason. Technical troubleshooting should precede another paid batch submission.

After recovery, repeat the delivery check: actual file count, readable downloads, approved versions and backup. Keep unresolved photos explicitly labelled rather than marking the whole archive accepted. A partial batch can finish as a useful subset while a few exceptions follow a different editing method.

## FAQs

Should I rerun all ten photos if two fail?

Keep successful files and investigate the unresolved items. Restart only the justified remaining scope.

Is a visually rejected image a technical failure?

No. A completed output can use a credit even when you reject its appearance.

Should a missing preview trigger immediate regeneration?

Check recorded status and existing downloads first. A display or download issue is not necessarily a generation failure.

Is failed-output credit release automatic?

The recorded settlement automatically returns reserved credits for technically failed restoration outputs. Check the final job state and settled balance; separate support adjustments and purchase-payment refunds are different matters.

## Sources

Preservation and technical guidance reviewed for this article.

- RestoreBunny: [Current credit-pack pricing](<https://restorebunny.com/pricing/>)
- RestoreBunny: [Credits, outputs and privacy FAQ](<https://restorebunny.com/faq/>)
- RestoreBunny: [Credit purchase and technical issue policy](<https://restorebunny.com/refund/>)
- RestoreBunny: [Image processing and retention policy](<https://restorebunny.com/privacy/>)

## Related

- [Restore a Photo Album with RestoreBunny: Credits, Settings and Downloads](<https://restorebunny.com/guides/restore-photo-album-with-restorebunny/>)
- [Photo Restoration Quality Checklist: What to Check Before Saving](<https://restorebunny.com/guides/photo-restoration-quality-checklist/>)
- [Review supported photo restoration](<https://restorebunny.com/features/photo-restoration/>)
- [Start an eligible restoration trial](<https://restorebunny.com/signup>)
- [Check current credit-pack terms](<https://restorebunny.com/pricing/>)
- [Use the family archive handoff worksheets](<https://restorebunny.com/resources/>)

## Ready to restore your photos?

Upload an image, choose your settings, and preview results with a before/after slider.

[Restore my photo](<https://restorebunny.com/signup/?from=seo-content&source=%2Fguides%2Frecover-partial-restoration-batch-before-paying%2F>)[View Pricing](<https://restorebunny.com/pricing/>)

RestoreBunny Team

Photo workflow editors

Guides follow our [editorial policy](<https://restorebunny.com/editorial-policy/>) for sourcing, product claims, AI limitations, updates, and corrections.
