Reconcile partial success by giving every accepted placement its own outcome and comparing those outcomes with the original batch membership. Confirmed posts stay confirmed, proven failures receive a recovery decision, and uncertain results remain unresolved. Never replay the whole batch simply because some items failed.
Which evidence matters first?
A batch status is a summary, not the primary record. Maintain the asset revision, destination, job reference, and evidence for each placement. This makes it possible to correct one account without changing work already completed on another.
How should the team handle the work?
Freeze the accepted batch membership for reconciliation. Identify which planned items were actually authorized and submitted.
Classify each placement from evidence: confirmed, processing, failed before publication, cancelled, or uncertain. Keep missing evidence visible.
Create recovery work only for the appropriate items, with links to the original intent. Reconcile again after recovery rather than replacing the earlier report.
What should the record show?
| Field | Purpose |
|---|---|
| Accepted membership | The placements actually authorized |
| Per-item result | Evidence and state at a stated time |
| Recovery linkage | New attempt tied to its original placement |
Keep the observation time alongside the outcome. A report is a snapshot of evidence, and later information may change the classification. Preserve the earlier state so a reviewer can understand what was known when a decision was made. This is especially useful when a customer and provider see different parts of the workflow.
What does a worked example look like?
In a hypothetical ten-placement batch, seven are confirmed, one is still processing, one failed before submission, and one has an ambiguous timeout. The team can investigate and repair the proven failure while leaving the confirmed seven alone. The processing and uncertain items need different follow-up checks.
What should you avoid claiming?
Do not report seven of ten as a final delivery rate while unresolved jobs can still change. Label the snapshot time and update it with subsequent evidence. AWS’s retry guidance provides background on why preserving request intent matters when recovering distributed operations.
For the wider workflow, read Why Is Scheduled Not the Same as Published?.
How can you validate the method on a small example?
Reconcile a sample batch twice: immediately after execution and after the recovery work finishes. Preserve the first snapshot and show which records changed as new evidence arrived.
Check that a recovery attempt does not increase the count of intended placements and that an unresolved item does not disappear from the denominator. Ask a reviewer to trace one final confirmation back through every attempt. The exercise passes when the batch total is explainable from its individual records and when completed work is not replayed merely to produce a cleaner group status.
How should the reconciliation table change after recovery?
Keep one row per intended placement and record attempts beneath it. In the hypothetical batch, the item rejected before submission is corrected and later confirmed. The batch still contains ten accepted placements; it does not become eleven because recovery created another request.
In Grafana’s 2026 infrastructure observability survey, 38% cited complexity and overhead as their biggest concern, and 30% identified alert fatigue as a response obstacle. Use those findings as a reason to consolidate recovery evidence into the placement record. They are not publishing-failure benchmarks.
| Record | First snapshot | Later observation |
|---|---|---|
| Placement 08 | Processing | Confirmed after inspection |
| Placement 09 | Rejected before submission | Corrected attempt confirmed |
| Placement 10 | Outcome uncertain | Still open, with an investigation owner |
The first seven confirmed placements remain untouched. The new snapshot can show nine confirmed and one unresolved, while retaining the earlier seven-confirmed record. Label the observation times so readers can understand why the totals differ.
If a correction changes the caption, destination, or time-sensitive offer, check approval before recovery. Reconciliation establishes what happened; it does not authorize a new creative decision. The approval workflow keeps that boundary explicit.
Where does Conbersa fit?
Conbersa provides managed social accounts for teams that supply finished content and direction. Posting and ongoing account activity are part of the offer. Agree the evidence, exception handling, and reporting you need before treating this recommended operating method as a provider commitment. Additional accounts do not guarantee reach or business results.