How to Retry Failed Snapshot Loads in Sparkforge

Snapshot Load Retry recovers failed sub-account pushes without forcing you to rebuild from scratch. Run it from Load History to retry only the failed accounts and watch progress update in real time.

What Snapshot Load Retry does

It re-runs the failed sub-accounts inside the original load attempt. Successful sub-accounts stay untouched. Retries stay grouped under the original load so audit history and troubleshooting context are preserved.

When to use it

• Temporary timeouts during a large rollout batch.
• Permission errors on a few sub-accounts you have since fixed.
• Intermittent network or API errors that broke the original push.

Where to find it

1. Open Snapshots in Agency view.
2. Click Load History.
3. Select the load that contains failed sub-accounts.
4. Open load details to see retry options.

Retry all failed sub-accounts

Use this when several sub-accounts in the same batch failed and you want one click to re-run them.

1. Open Snapshots → Load History.
2. Click the load with failed sub-accounts.
3. Click Retry All Failed.
4. Watch statuses update as Sparkforge retries the failed items.

Retry specific sub-accounts

Use this after fixing a known issue on a few accounts (for example, a permission you corrected).

1. Open Snapshots → Load History and select the load.
2. Expand the batch to see the sub-account list.
3. Check the box next to each failed sub-account you want to retry.
4. Click Retry Selected.

Track retry progress

Status indicators update in the same load details view as retries run: In Progress, Successful, Failed. You don't need to switch pages or restart the push.

When retry is unavailable

• 48-hour limit: loads older than 48 hours can't be retried. Create a new load instead.
• Snapshot changed: if the underlying snapshot was refreshed or modified after the original load, start a new load so the latest version applies.