Resume Interrupted Batch Jobs in XERIA

Long PDF batch operations do not always have to finish in one uninterrupted session. XERIA can pause an active batch, save it for later continuation, detect recoverable unfinished jobs and resume the remaining work through Resume Center.

This is useful when a large personalized PDF job takes longer than expected, a workstation must be shut down, a mail or cloud connection needs attention, or an operation is deliberately postponed.

What You Will Learn

This tutorial explains how to:

• Pause an active batch without immediately terminating it
• Continue a paused batch in the same session
• Save a running or paused job with **Continue Later**
• Understand when XERIA finishes the current item before pausing or saving
• Find unfinished work in **Resume Center**
• Read remaining-recipient and last-update information
• Resume **Generate PDF**, **Generate PDF + Send**, and **Send email only** jobs
• Use the **Resume Checklist**
• Resolve source PDF, output folder, watermark, security, mail and recipient-list differences
• Reconnect cloud or mail dependencies when required
• Continue with saved settings
• Restart with current settings when the original job should no longer be resumed
• Delete an unfinished job
• Distinguish recoverable interruption from a deliberate stop

For general batch production, see [Batch PDF Watermarking](/resources/articles/batch-pdf-watermarking/).

Why Batch Recovery Matters

A personalized batch can involve:

• Many recipients
• Large source PDFs
• Watermark rendering
• Password protection
• Permission restrictions
• QR trace elements
• Local or cloud output
• Email delivery

A long-running job can therefore depend on several resources at once.

If work is interrupted after some recipients are already complete, starting the entire batch from the beginning can create duplicate outputs, duplicate mail attempts or unnecessary processing.

XERIA’s recovery workflow is designed to preserve the identity and progress of unfinished work so the remaining recipients can be handled deliberately.

Three Different Ways to Interrupt an Active Job

During a controlled batch operation, XERIA provides three distinct controls:

Choose the control that matches your intention.

Do not use **Stop Operation** when you actually intend to resume the unfinished recipients later.

How Pause Works

Select **Pause** while the batch is running.

XERIA does not normally interrupt the item currently being processed in the middle of its work.

Instead, the interface reports that the pause has been requested and that the operation will pause after the current item completes.

This reduces the risk of leaving the current recipient or output in an ambiguous partial state.

When the pause becomes active, XERIA reports that the operation is paused.

At that point, you can:

• Select **Continue** to resume immediately
• Select **Continue Later** to save the unfinished job
• Use **Stop Operation** if the job should not be recoverable later

Continue a Paused Job Immediately

If the interruption is temporary, use **Continue**.

Typical reasons include:

• Checking another application
• Confirming available disk space
• Reviewing a generated sample
• Waiting briefly for another process
• Temporarily reducing system load

When you continue, the active batch proceeds from its controlled execution state.

There is no need to create a Resume Center entry merely for a short pause.

Use Continue Later for a Planned Interruption

Select **Continue Later** when the current session should end but the unfinished work must remain recoverable.

Continue Later can be requested while the job is:

• Running
• Paused
• Waiting for a requested pause to take effect

XERIA saves the operation after the current item completes.

The active progress window then closes, and the unfinished job becomes available through the recovery workflow.

A job deliberately saved this way is identified as having been saved by the user to continue later.

When Continue Later Is Useful

Use Continue Later when:

• A large job must continue another day
• The workstation must be restarted
• You need to leave before processing completes
• A cloud dependency needs to be restored
• Mail delivery configuration requires attention
• You want to inspect completed outputs before continuing
• The remaining recipients should be processed in a later session

Continue Later is an operational checkpoint, not a substitute for backing up source documents or recipient data.

Understand Stop Operation

**Stop Operation** deliberately ends the active job.

XERIA asks for confirmation before stopping.

The confirmation explains two important consequences:

• Outputs already completed are kept
• The job will not be listed for later continuation

The stop request takes effect after the current item completes.

Use Stop Operation when:

• The batch was started by mistake
• The recipient selection is wrong
• The source document is wrong
• The output policy has changed
• The current unfinished job should be abandoned
• You intend to configure and start a completely new job

Do not use Stop Operation merely because you want to shut down the computer and resume later.

What Resume Center Shows

Resume Center is XERIA’s modern recovery interface for unfinished jobs.

When recoverable work exists, Resume Center can present an **Unfinished Batch Job** card with information such as:

• Total recipient count
• Completed recipient count
• Remaining recipient count
• Last update time
• Original start action

For a job explicitly saved with Continue Later, the summary can also indicate that it was saved by the user to continue later.

Recoverable batch cards are ordered with the most recently updated work first.

Resume Center can also contain unfinished folder-watermark jobs. This tutorial focuses on recipient-based batch jobs.

Supported Batch Actions

Resume Center preserves the original batch action.

For recipient batch jobs, the action can be:

• **Generate PDF**
• **Generate PDF + Send**
• **Send email only**

This distinction matters.

A resumed generation job should continue generation.

A resumed generation-and-send job must also satisfy its mail prerequisites.

A resumed send-only job depends on the correct existing PDF attachments and mail configuration.

For email-specific preparation, see [Send Personalized PDFs by Email with XERIA](/resources/articles/send-personalized-pdfs-by-email-with-xeria/).

Opening Resume Center

When recoverable jobs exist, XERIA exposes unfinished work through Resume Center.

At application startup, the recovery system can check for unfinished jobs and open Resume Center without relying on the retired legacy batch-resume popup.

Resume Center provides three primary choices:

• **Continue**
• **Delete**
• **Later**

Select a job before choosing Continue or Delete.

Choose Later when you want to leave the recoverable job unchanged and return to it another time.

Step 1: Select the Unfinished Job

Open Resume Center and review the available cards.

For the intended batch, confirm:

• Job type is Batch
• Remaining-recipient count is plausible
• Total-recipient count matches the expected job
• Last update time is consistent with the interrupted session
• Start action matches the operation you were performing

Do not continue the first card automatically if more than one unfinished job exists.

The most recently updated job is shown first, but that does not guarantee it is the one you intend to resume.

Step 2: Select Continue

Choose the intended unfinished batch and select **Continue**.

XERIA then opens the Batch area and builds a **Resume Checklist**.

The checklist is important because the environment may have changed since the job was interrupted.

A source file may have moved.

The recipient list may have changed.

Mail authentication may have expired.

A cloud provider may no longer be connected.

Watermark or security settings may differ from the saved job.

Resume should therefore be a validation process, not a blind restart.

What the Resume Checklist Compares

The checklist can evaluate areas including:

• Start Action
• Source PDF
• Output Folder
• Watermark Image
• Watermark Settings
• Security and Permission Settings
• Mail Settings
• Recipient List
• Mail Channel

The exact checks depend on the unfinished job.

A generation-only job does not have the same operational dependencies as a generation-and-send or send-only job.

Source PDF Check

XERIA checks whether the source PDF used by the unfinished job is still available.

Possible conditions include:

• Saved source path is missing
• Source PDF cannot be found
• Source PDF exists but appears to have changed
• Source PDF exists and matches the saved job metadata

Do not resume a sensitive batch with a different source document merely because the filename looks similar.

A changed source can produce different output for the remaining recipients than for the recipients already completed.

Output Folder Check

The output destination is also reviewed.

The checklist can distinguish between:

• The expected output folder being available
• The output folder being inaccessible or missing
• The current output folder differing from the unfinished job

This matters because the resumed job should preserve a coherent output set.

Before continuing, verify that:

• The destination is writable
• Existing completed outputs are still present where expected
• The resumed files will not be written to an unintended location
• Local or cloud destination access is available

Watermark Image Check

If the unfinished job used an image watermark, XERIA can check whether that image is still available and whether it appears to have changed.

Possible results include:

• No image watermark was used
• Image file cannot be found
• Image exists but has changed
• Image exists and matches the saved metadata

Replacing the image watermark during a resumed job can make the remaining outputs visually different from those already completed.

Watermark Settings Check

XERIA compares the current watermark settings with the unfinished job.

Differences can involve settings such as:

• Watermark text
• Font
• Color
• Opacity
• Angle
• Position
• Tiling
• Image watermark configuration

A warning does not always mean continuation is impossible.

It means you should decide whether to resume the original job identity or intentionally restart using the current settings.

For personalized watermark design, see [Create Personalized PDFs in XERIA](/resources/articles/create-personalized-pdfs-in-xeria/).

Security and Permission Check

The checklist can compare current PDF security and permission settings with those saved for the unfinished job.

Review differences carefully when the job uses:

• PDF encryption
• Open passwords
• Owner passwords
• Permission restrictions
• Permission profiles
• Hidden QR trace elements

The recipients processed after the resume should not silently receive weaker or different protection than recipients completed before the interruption.

Recipient List Check

XERIA also compares the current recipient list with the unfinished job.

Do not casually add, remove or reorder recipient records while planning to resume.

A changed list can affect:

• Recipient identity
• Output filename
• Watermark data
• Password mapping
• Trace information
• Email address
• Attachment mapping

The point of a normal resume is to continue the unfinished job, not redefine its recipient population.

Mail Settings and Mail Channel Checks

For **Generate PDF + Send** and **Send email only** jobs, mail configuration is part of the recovery decision.

XERIA can compare mail settings and verify that a valid mail channel is available.

If the original mail channel is no longer available, the checklist can require a new mail channel before continuation.

Mail-related saved information can include subject, body, HTML-body mode, signature and default channel identity.

Do not continue a send-capable job until the intended sender and message configuration are confirmed.

Cloud Connections

A recovery checklist may discover that a required cloud provider is no longer connected.

The recovery workflow can provide actions for reconnecting services such as:

• Dropbox
• OneDrive
• Google Drive

After reconnecting, refresh the checklist and review the state again.

Do not bypass a missing cloud dependency by redirecting the job to a different location unless that is an intentional restart decision.

Refresh the Checklist

Use the checklist refresh action after correcting a dependency.

Typical sequence:

• Fix the missing source or output access
• Reconnect the required service
• Correct the mail configuration
• Restore the expected recipient data
• Return to the checklist
• Refresh the checks

Continue only after the important prerequisites reflect the state you intend to use.

Change Settings

The recovery workflow can direct you to the relevant settings area when a saved job and the current application state differ.

Use this path when you need to inspect or correct:

• Watermark settings
• Source template
• Output destination
• Security settings
• Mail settings

After changing settings, return to the unfinished job and rebuild the checklist.

Changing settings does not automatically mean that the old job should be resumed.

The checklist exists so you can make that decision explicitly.

Continue with the Saved Job

When the checklist is acceptable, choose **Continue**.

XERIA builds an execution plan for the unfinished job and resumes through the recovery orchestrator.

The modern recovery context is the authority for progress.

For a recipient batch, completed progress corresponds to the saved point in the recipient sequence, and the job continues with its remaining work rather than blindly restarting the entire list.

The execution plan is also applied to the interface for visual consistency, while the resumed production settings come from the recovery execution context.

Restart with Current Settings

Sometimes the right decision is not to resume the original job.

The Resume Checklist can support **Restart** with the current settings.

This is fundamentally different from normal resume.

When restarting with current settings:

• The old unfinished job is cancelled and removed after restart prerequisites are ready
• It does not continue from only the remaining-recipient list
• A new normal batch operation starts
• The original action type is preserved: Generate PDF, Generate PDF + Send, or Send email only

Use Restart when the settings have intentionally changed and all recipients should be processed under the new configuration.

Do not choose Restart if your goal is simply to process the unfinished recipients from the saved job.

Important Difference: Resume vs Restart

This distinction prevents a changed configuration from being silently mixed into an existing partial batch.

Delete an Unfinished Job

Resume Center also provides **Delete**.

Use Delete when the saved unfinished job is no longer needed.

Deleting a recoverable batch removes it from the recovery workflow.

Use this when:

• The job is obsolete
• A replacement batch has already been completed
• The source or recipient population is no longer valid
• You deliberately want to discard the unfinished recovery state

Do not delete a job merely to close Resume Center. Use **Later** instead when you may still need the job.

What Happens to Completed Outputs?

When an active job is paused or saved for later, items already completed remain completed.

When **Stop Operation** is used, completed outputs are also kept, even though the job itself is not preserved for later continuation.

This means file-system cleanup is a separate decision from recovery-state cleanup.

Before restarting an entire job, review existing outputs so you understand whether the normal pipeline will create, replace or conflict with files already present.

Resume Generate PDF Jobs

For a **Generate PDF** job:

• Confirm the source PDF
• Confirm the recipient list
• Confirm the output destination
• Confirm watermark settings
• Confirm security settings
• Review remaining-recipient progress
• Continue through the checklist

The resumed operation then focuses on the unfinished work.

Resume Generate PDF + Send Jobs

For a **Generate PDF + Send** job, all generation checks still matter, plus mail dependencies.

Confirm:

• Sender profile
• Mail channel
• Subject
• Body
• Signature
• Authentication
• Recipient email addresses
• Output and attachment behavior

A PDF generation environment may be ready while the mail environment is not.

Resolve both sides before continuing.

Resume Send Email Only Jobs

For a **Send email only** job, the existing attachments are especially important.

Confirm:

• Each remaining recipient still points to the correct PDF
• Required files still exist
• File paths have not changed
• Mail settings are correct
• Sender authentication is valid
• The remaining-recipient count is plausible

Do not substitute attachments from another recipient just to satisfy a missing-file check.

After the Resume Starts

Monitor the resumed operation as you would a normal batch.

Watch:

• Current item
• Completed count
• Remaining work
• Errors
• Output location
• Mail failures where applicable
• Cloud connectivity where applicable

The batch controls remain relevant during resumed execution.

You can pause again, continue again, or save the job for later if another planned interruption is necessary.

Common Problems

Resume Center Does Not Show the Job

The job may have:

• Completed normally
• Been stopped with Stop Operation
• Been deleted
• Been restarted as a new job
• No remaining recoverable work

Remember that Stop Operation deliberately does not retain the job for later continuation.

The Source PDF Cannot Be Found

Restore the original source PDF to an accessible location or use the recovery settings workflow to resolve the source requirement.

Do not silently substitute a different document.

The Source PDF Has Changed

Determine whether the change was intentional.

If the remaining recipients must receive the new version, Restart with current settings may be more appropriate than normal resume.

The Output Folder Is Missing

Restore access to the intended destination or deliberately change the job configuration through the recovery workflow.

Watermark Settings Differ

Review whether the current settings were changed accidentally or intentionally.

Use the saved recovery context for normal continuation, or Restart if all recipients should be processed under the new settings.

Recipient List Differs

Restore the intended recipient context before normal continuation.

If the recipient population has intentionally changed, consider a new or restarted batch rather than mixing populations inside one interrupted job.

Mail Channel Is Not Available

Open mail management, restore or replace the required channel, then refresh the Resume Checklist.

Cloud Provider Is Disconnected

Reconnect the required Dropbox, OneDrive or Google Drive service through the recovery workflow, then refresh the checklist.

I Clicked Stop Operation Instead of Continue Later

The completed outputs remain, but the stopped job is not retained as a recoverable job.

A new batch may be required for the unprocessed recipients.

I Want to Close Resume Center Without Deleting Anything

Choose **Later**.

The recoverable job remains available.

Best Practices

• Use Pause for short interruptions.
• Use Continue Later for planned session breaks.
• Do not use Stop Operation when you intend to resume later.
• Let the current item finish before expecting pause or save to complete.
• Review remaining-recipient counts before resuming.
• Confirm the original start action.
• Keep source PDFs unchanged during unfinished jobs.
• Keep output destinations available.
• Avoid editing recipient lists during a recoverable batch.
• Preserve watermark and security settings.
• Protect password and permission mappings.
• Keep required cloud accounts connected.
• Verify mail authentication before resuming send-capable jobs.
• Use Resume Checklist warnings as decision points.
• Refresh the checklist after fixing dependencies.
• Resume when you want only the unfinished work to continue.
• Restart when you intentionally want a new full run with current settings.
• Use Later instead of Delete when you are undecided.
• Delete obsolete recovery jobs.
• Review completed outputs before starting a replacement job.
• Monitor resumed operations just like normal production.
• Review Mail Log after resumed email delivery.

Frequently Asked Questions

Can XERIA Resume an Interrupted PDF Batch?

Yes. Recoverable unfinished batch jobs can be listed in Resume Center and continued after their prerequisites are reviewed.

What Does Continue Later Do?

It requests that the current item finish, saves the unfinished job and makes it available for later continuation through the recovery workflow.

Does Pause Save the Job for Another Day?

Pause is primarily an in-session control. From the paused state, choose Continue Later when you want to save the job for a later session.

Does Stop Operation Create a Recoverable Job?

No. Completed outputs are kept, but the stopped job is not listed for later continuation.

Does XERIA Resume from the Beginning?

A normal resume uses the saved recovery progress and continues the unfinished work rather than simply starting the entire recipient list again.

What Information Does Resume Center Show?

For a batch job it can show total, completed and remaining recipients, last update time and the original start action.

Can XERIA Resume Generate-and-Send Jobs?

Yes. Resume Center recognizes Generate PDF, Generate PDF + Send and Send email only batch actions. Mail prerequisites must be valid for send-capable jobs.

What If My Settings Changed?

The Resume Checklist compares relevant current settings with the unfinished job. You can resolve the difference and continue the saved job, or intentionally restart with current settings.

What Is the Difference Between Resume and Restart?

Resume continues the saved unfinished work. Restart cancels the old recoverable job and begins a new normal batch using current settings.

Can I Leave Resume Center Without Making a Decision?

Yes. Choose Later to keep the job available.

Conclusion

XERIA’s recovery workflow makes long batch processing more manageable by separating temporary pause, planned continuation and deliberate cancellation.

Use **Pause** when you only need a short break. Use **Continue Later** when the unfinished job should survive beyond the current session. Use **Stop Operation** only when the job should end and should not appear in Resume Center.

When you return, Resume Center shows recoverable work and its remaining progress. The Resume Checklist then checks the source PDF, output destination, watermark settings, security settings, recipient list, mail configuration and other dependencies before execution continues.

The key decision is whether you are continuing the original unfinished job or intentionally starting a new run. Resume preserves the saved job context and remaining work; Restart with current settings creates a new normal batch under the configuration you have now.