Snapshot Load Retry

The Snapshot Load Retry feature helps you quickly recover from failed snapshot pushes without starting over. If a snapshot push doesn’t go through for all sub-accounts, you can now retry failed accounts directly from your push history.

Overview

Previously, when a snapshot push failed, you had to:

• Identify which sub-accounts failed

• Go back to the snapshot

• Create a brand-new Load

With Snapshot Load Retry, retries happen exactly where the failure occurred — saving time, clicks, and effort.

Where to Find Snapshot Load Retry

1. Go to Snapshots

2. Open Load History
   

3. Select a snapshot push with failed sub-accounts

4. Use the Retry options available within the batch

How Snapshot Load Retry Works

When a snapshot push contains failures, you’ll see retry options directly in the View History page.

Option 1: Retry All Failed Sub-Accounts

Use this option when you want to retry every sub-account that failed in the batch.

Steps:

1. Open the snapshot push from Load History

2. Click Retry All Failed

3. The system will retry only the failed sub-accounts

4. Progress and results will update in real time on the same page

Option 2: Retry Specific Sub-Accounts

Use this option when only certain sub-accounts need to be retried.

Steps:

1. Open the snapshot push from Load History

2. Click into the batch details

3. Select the specific sub-accounts you want to retry

4. Click Retry Selected

5. Track retry progress directly from the batch view

Tracking Retry Progress

• Retry attempts appear under the same original Load

• Status updates in real time (In Progress, Successful, Failed)

• You don’t need to refresh or navigate away from the page

This keeps all related attempts grouped together for better visibility and organization.

When Retry Is Not Available

To ensure data accuracy and consistency, retries are disabled in the following cases:

1. Load Is Older Than 48 Hours

• Snapshot pushes can only be retried within 48 hours of the original push

• Older pushes will require creating a new snapshot push

2. Snapshot Has Been Updated or Refreshed

• If the snapshot was refreshed or modified after the original push

• Retries are disabled to prevent loading outdated data

• You’ll need to start a new push to use the latest snapshot version

Why These Limits Exist

These safeguards ensure:

• Sub-accounts receive the most accurate and up-to-date snapshot data

• Partial or outdated configurations aren’t re-applied unintentionally

• Load history remains reliable and auditable

Benefits of Snapshot Load Retry

• Save Time – No need to recreate snapshot pushes

• Reduce Manual Effort – Retry failures in just a few clicks

• Stay Organized – All retries remain linked to the original push

• Faster Recovery – Quickly resolve temporary errors or permission issues