Aria Sync Re-processing
This section details the information the usage operator needs to view, review, and reprocess synchronization records, errors, and their reprocessing between core Aria and Aria Allegro.
This section details the information the usage operator needs to view, review, and reprocess synchronization records, errors, and their reprocessing between core Aria and Aria Allegro.
This section covers the following topics:
- Manage catalog sync data from core Aria to Aria Allegro
- Manage account sync data from core Aria to Aria Allegro
- Manage monetized usage data from Aria Allegro to core Aria
Some failure causes and their resolutions overlap. These integrations rely heavily on the KAFKA topic framework, so configuring the consumer and producer sides of relevant KAFKA topics is crucial. Ideally, issues should be resolved during initial setup, deployment, and testing.
The remaining sub-sections may seem repetitive, but we document them to maintain independence.
- Catalog Sync
- This sub-section details the activity log for Catalog sync Data feed LOM messages related to Aria Product Catalog items relevant to Aria Allegro.
- Account Sync
- This article describes how Aria Allegro logs and manages Account Sync data feed messages from core Aria, including which objects are synchronized, available status values, and how to search, sort, and filter activity logs. It also explains how to view detailed payloads, interpret and resolve common sync errors, and reprocess failed Account Sync messages at multiple levels using the Reprocess Summary and Activity views.
- Aggregated Usage Record Sync
- This article explains how Aria Allegro synchronizes aggregated billing usage records with core Aria via a synchronous bulk_record_usage_m API call, and how errors are surfaced based on messages returned by the core API. It also describes how to view incomplete or errored aggregated usage batches, interpret their status values, use filters and sorting, and reprocess failed records at various levels.