Challenge

When sending rated Usages, we might be unable to aggregate them successfully. You can see the successful aggregation in the Rated Usages status.

How does it work

Status model

Status definitions

Status	Description
`PENDING_NEW`	Usage is created and is currently being attempted to be aggregated.
`PENDING_RETRY`	Usage could not be aggregated and is currently being attempted to be aggregated.
`AGGREGATED`	Usage is successfully aggregated.
`CANCELLED`	An already aggregated Usage has been cancelled and removed from the latest aggregation result.
`UNPROCESSED`	Usage could not be aggregated. Aggregation can be retried either automatically (until max attempts are exceeded) or manually.
`DISCARDED`	Usage is not considered when automatically retrying aggregation. Manual retry will restart the automatic retries from the beginning.

Failed Aggregation

The reasons for a failed aggregation are usually

The contract does not exist.
The contract does not contain the Rated Usage Option

Automatic Retry policy for failed Usages

A total of 10 attempts are made. The first attempt is executed immediately, and on the final attempt, the rated usage is set to the status DISCARDED. Subsequent retries are initially delayed by 10 minutes, with the delay doubling after each attempt. However, the maximum delay for the next attempt is capped at 12 hours.

Retry after discarded

If a Rated Usage ended up in the discarded status, we will make no further attempts to aggregate. If you've solved the problem (creating the correct contract for example), you can manually retrigger the retry, which will restart the automatic aggregation from the beginning.