Retry a Partially Successful Integration Safely
Retry a Partially Successful Integration Safely
Overview
This guide will help you retry only failed integration records while protecting successful records from duplication.
Failed records are recovered without intentionally duplicating accepted transactions.
Who can do this
You need access to Relevant execute/retry permission plus inquiry/history.
Before you start
Classify each record as successful, rejected, failed before submission, unknown, or locally inconsistent; keep all IDs and responses.
Before saving, check that the correct company is open and that you have permission to complete this task.
Where to find it
Open the integration's inquiry, synchronization result, or failed-record list.
Retry a Partially Successful Integration Safely
Step 1: Freeze the original batch evidence
Step 2: Exclude confirmed-success records
Step 3: Query unknown outcomes by external ID before resubmission
Step 4: Correct deterministic validation or mapping failures
Step 5: Retry one failed record first
Step 6: Reconcile provider and Muhasib state
Step 7: Process remaining eligible failures once
Process remaining allowed failures once.
Check your work
Every source record maps to no more than one accepted external/local result and the control count/value reconciles.
Take a moment to check your work before closing the window. This small check can save time later.
If something goes wrong
- Stop on duplicate-key or already-processed responses.
- Escalate local/provider state disagreement instead of deleting either side.
Related guides
- Diagnose an External Integration Failure
- Recover from Partial Offline POS Synchronization
- Recover from Tax Submission Failure