-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
fine-grained-payg-errors
-
False
-
-
False
-
To Do
-
100% To Do, 0% In Progress, 0% Done
In some cases, we have a very broad failure type, and we can be more nuanced with our representations of the error, in order to more quickly triage the issue. Specifically, with contracts, we know of three possible types of errors:
- There is no contract record for the billing account ID.
- The usage is for a Red Hat organization not authorized to use the associated contract. (The contract record for a given billing account ID belongs to a different Red Hat organization than the usage record).
- A contract record has expired.
Any time we look up a contract, we should emit distinct errors for these conditions.
- relates to
-
SWATCH-2173 Design resilience document for handling failures in different Marketplace Billable Usage
- Closed