Sync Executions

A sync execution is a per-scope observation tied to its parent integration definition. It records a source record identity, schedule, outcome, counts, errors, mapping version and source and destination watermarks. The synchronization workflow reserves and confirms that output as it executes a reviewed revision. The Integration Operator checks it alongside the delivery attempt and operation run before accepting the operating result.

A definition may look complete while a scope is rejected or an attempt has failed. The per-scope record helps the operator find the affected source identity and determine whether the destination accepted the work. The external request reference and receipt on the run step connect the app’s observation to the other system’s acknowledgement.

• Scoped output. Each observed source record identity stays linked to the definition and its mapping version.
• Delivery attempt. Attempt number, provider reference and failure reason make retries and uncertain outcomes visible.
• Reconciliation. Counts, errors and paired watermarks show whether the source and destination moved together.

The operator should review an Unknown attempt as unresolved. The current definition status does not answer whether the provider received that particular attempt. Use its operation key, provider reference and receipt evidence to investigate before starting work that could duplicate a destination change.

Define the scope of a sync observation for each pipeline: a source record, batch or other unit represented by its source identity. Agree which system supplies the authoritative receipt and how the operator obtains it. Set a procedure for comparing the watermarks and counts, including what creates a follow-up action. Choose who can rerun work after a failed or uncertain attempt and what they must check first.

Review the schedule with the business owner. A completed run needs enough time for the destination to provide its result before the operating day closes. Keep mapping versions stable during a reviewed run so a rejected output can be reproduced and corrected against the same contract.

Suppose a scheduled customer update reaches the destination, but one source record is rejected. The operator opens Sync Outcome Review to identify the affected source record and its mapping version. In Delivery Attempts, they find the attempt number and provider reference. The run trace shows the step’s output reference and external receipt. Together these records distinguish an actual rejection from a missing acknowledgement.

The operator records the unresolved failure for follow-up and brings the owner into a correction decision. If compensation is needed, the correction workflow retains the executed revision and creates a successor and explicit compensating output. The reviewer sees the new revision and evidence before work proceeds. The original attempt and receipt remain part of the explanation of why the correction was necessary.

• Sync Outcome Review — Per-scope outcomes with counts, errors and mapping version.
• Delivery Attempts — Attempts that are queued, running, failed or uncertain.
• Run Exceptions — Failed runs and work requiring reconciliation.

Follow synchronization and reconciliation or correction when an executed result needs a successor revision.