Step 9 — Run Your First Sync
After deploying AOH Sync and completing system setup, this guide walks you through triggering your first sync and verifying the results.
Before starting this guide, confirm your source, target, and provisioning Connector are set up — covered in Step 6 — Connect a Source System, Step 7 — Connect a Target System, and Step 8 — Set Up Provisioning.
Confirm your Connector's Field Mappings
Open Connectors in the left sidebar and select the Connector that links your Source System to your Target System. Navigate to the Field Mappings tab.
Review each mapping to make sure source fields are mapped to the correct target attributes. Pay particular attention to the fields that drive identity matching — typically a unique identifier such as an employee ID or email address. Incorrect mappings here will cause data to land in the wrong attributes or prevent records from being matched on subsequent syncs.
Make any needed adjustments, then save your changes. AOH Sync records each change in Revisions & History, giving you an audit trail of every mapping change.
Set a Schedule or use Run Now
Navigate to the Schedule tab on the same Connector.
To run the sync immediately without waiting for a scheduled window, use the Run Now option on the Connector. This is the fastest way to validate your configuration.
To set a recurring sync cadence, configure your schedule here. AOH Sync will run the Connector automatically at the interval you specify.
For your first sync, using Run Now lets you see results quickly and catch any mapping or connection issues before committing to a schedule.
Watch progress in Sync History
After triggering the sync, go to the Sync History tab on the Connector. The log updates as the sync runs and shows each record processed, the action taken (created, updated, skipped, or errored), and any warnings.
If errors appear, expand the affected rows for details. Common causes include:
A source field mapped to a required target attribute that is empty or missing for some records.
A connection interruption to the Source System or Target System.
A field type mismatch between the source value and the expected target format.
Address any errors, then re-run if needed.
Verify results on the Dashboard and in Browsing Identities
Once the sync log shows completion, verify the results in two places:
Dashboard — Check the summary metrics to confirm the expected number of Identities and Accounts are reflected. The Dashboard updates after each sync run.
Browsing Identities — Browse the Identities list to spot-check a few records. Confirm that the attributes from your Source System are present and correctly populated on each Identity's detail view.
If the counts or attribute values look wrong, return to Field Mappings and adjust, then run again.
Related
Last updated