Allegro FAQ
The purpose of this page/section is to not only look at errors and reprocessing but also provide answers to general frequently asked questions.
- Allegro FAQ
- This article provides a detailed FAQ-style overview of Aria Allegro, covering deployment model, usage ingestion, file handling, pricing, pooling, and balance management behaviors. It explains how Allegro interacts with core Aria, including multi-tenant support, roadmap dependencies, configuration requirements, and key rules for dates, tiers, rounding, and future features like APIs, sharing groups, and volume rating.
Error handling and reprocessing are covered in the following sections:
- Usage Suspense Management in Usage Operations—error handling for usage suspense records.
- Aria Synchronization and error management in Aria Sync Re-processing, covering:
- Account synchronization errors—resolving errors for account and subscription data feed LOMs.
- Catalog synchronization errors—resolving errors for supported catalog components.
- Billing aggregated usage errors—reviewing and reprocessing billing aggregated usage synchronization from Aria Allegro to core Aria via the bulk_record_usage_m API.
Refer to 0. Allegro Architecture for descriptions of Aria Allegro components and potential failure points. All errors fall into two categories:
- Deployment and setup errors—these errors occur most often during new deployments or new client setups and may continue with new services or upgrade scripts in each release. Most minimize or are eliminated as the platform matures. Quick tests or automated tests can also prevent these errors.
- Functional errors—these errors result from misconfiguration or incorrect assumptions. A client go-live project using the Stage Current environment eliminates most of these issues before production. These also minimize with greater familiarity with Aria Allegro components.
In addition to error handling and reprocessing guidance, this section answers general frequently asked questions about Aria Allegro.