/ /
Airsync 201 – Mappings, sync metadata, and troubleshooting
In the Airsync 101 – Connect and import course, you learned how to set up Airsync integrations, create external connections, run imports, manage sync operations, and monitor sync status. This course is your next step, focused on understanding how the sync engine works behind the scenes.
In this course, the focus shifts from operations to architecture and troubleshooting. You will explore domain mappings, field-level configuration, sync metadata, and failure diagnosis to better understand how Airsync processes and transforms data.
Learning objectives
By the end of this course, you will be able to:
Explain the four-step domain mapping pipeline and how external schemas become transformation recipes.
Describe how Chef UI and Chef CLI are used to create, validate, and merge initial domain mappings.
Configure field mappings for complex cases including enum value mapping, array-to-single-value fields, and fallback values.
Explain how custom fields are dynamically extracted at runtime and automatically reversed in sync.
Read and interpret sync metadata on records, including the four sync statuses (succeeded, modified, staged, failed).
Use sync metadata filters in vistas and the works.list API to isolate records by source, sync unit, and status.
Identify staged and modified records, explain why they occur, and guide customers on resolution.
Diagnose a sync failure using Datadog, filtering by run ID, reading phase reports, and narrowing the root cause.
Was this article helpful?