View metered usage processing status

You can view if the metered usage is processed successfully, view errors, and manage failures (for details on errors, see Fix metered usage errors) using the following two options:

• User interface (UI) on the Metered usage page.
• Metered usage V2 API. For more information on how to check the metered usage processing status if using V2 API, see Fetch usage processing status.

The Metered usage page (UI) displays the processing status for usage submitted:

• With Metered usage V2 API
• By AppDirect, for Infrastructure as a Service (IaaS) billing products such as Google Cloud Platform, Azure, and Amazon Web Services pay-as-you-go. For details on IaaS metered usage processing, for more information, see View IaaS billing metered usage processing status.

The Metered usage page displays the following information, depending on your role:

• Marketplace Managers: Every metered usage request submitted to the marketplace.
• Developers who belong to a Developer company that owns products: Every metered usage request submitted to the marketplace for their products.
• Developers who belong to the company that owns the marketplace: No access to the Metered usage page.

The metered usage details page makes it easier to navigate usage data and identify subscriptions or customers that were missed in the monthly billing process because they were not available in the marketplace. Request details can include pending accounts and estimated unbilled cost for those accounts. You can reprocess filtered usage after you migrate the related subscriptions—see Reprocess pending migration usages.

To check metered usage processing status and errors from the UI

1. Go to Manage > Marketplace > Dashboard | BILLING | Metered Usage.
   The Metered usage list page opens and displays teh following columns:

   • Request details - This column displays:
     • Request identifier - System-generated identifier for the request returned in a response OR Group Request Identifier - Caller-generated identifier submitted with related requests to associate them (for example, all requests submitted for a particular billing period), and Date and time the request was submitted.
   • Request status - This column displays the status of the process:
     • In progress - Usage processing is underway.
     • Completed - All usage events in the request were processed successfully.
     • Failed - One or more usage events in the run were not processed successfully.
   • Process Date - Date and time run processing finished.

2. Click a request, or request group, row. The request details page opens. Based on the status, the following information is displayed on the Request summary pane:

   • Request ID
   • Date and Time
   • Total usage events received
   • Total pending accounts—Accounts that have not been migrated to the marketplace.
   • Total estimated cost for pending migration—The total amount that is not billed because the accounts have not been migrated to the marketplace.

   Based on the status of the request, the following tiles are displayed:

   • Pending Migration
   • Processing
   • Successful
   • Failed
   • Ready
     For details about the information that appears on this page, see the Request details section below.

3. To view events in each tile, click View All in the required tile or click the required tab in Usage Requests section. The list of events for the selected option is displayed in the table with teh following details:

   • Request Details - Details of the event such as date, time, and request ID.
   • Request ID
   • Usage Events

4. For details that appear in the Failure tile or tab, see the Failed event errors section below.

5. For details that appear in the Pending Migration tile or tab, see the Reprocess pending migration usages section below

You can also reprocess system errors; for details, see Fix metered usage errors. To reprocess usage that was filtered for pending migration, see Reprocess pending migration usages.

Reprocess pending migration usages

Usage records can be filtered during processing when the associated subscriptions are not available in the marketplace. After you migrate those subscriptions, you can reprocess the filtered usage from the Metered Usage page so the pending amount is billed with the current billing cycle. This avoids backend intervention or support tickets.

📝 Note: You must migrate the subscriptions to the marketplace before you can reprocess.

To reprocess pending migration usages

1. Migrate the subscriptions by using the migration tool at Manage > Marketplace > Settings > Migration. For more information about migration, see Migrate external company data.
2. Go to Manage > Marketplace > Dashboard | BILLING | Metered Usage.
3. Click the required row from the list page.
4. Do one of the following:
   • Click View All in the Pending Migration tile.
     OR
   • In the Usage Requests section, click the Pending Migration tab.
     The list of events pending migration is displayed with details such as the product name, number of usage events unbilled for that account and the estimated cost.
5. Select the account, then click Reprocess.

The pending amount is processed with the current billing.

Metered usage processing information that appears in the UI

Request details

The request details page displays additional information about a request.

Request summary pane	Request ID Request identifier—System-generated identifier for the request returned in a response Group Request Identifier—Caller-generated identifier submitted with related requests to associate them (for example, all requests submitted for a particular billing period) Request status In progress—Usage processing is underway Run Completed—All usage events in the run were processed, successfully or not Failed—All usage requests in a usage submission run failed Date and time the request was submitted Total usage events received—Number of usage events submitted with the request Total pending accounts—Accounts that have not been migrated to the marketplace and whose usage was filtered from billing Total estimated cost for pending migration—Estimated amount that is not billed because the accounts have not been migrated to the marketplace
Request processing status tiles	Pending Migration - Number of accounts pending migration, including the product name, the number of usage events unbilled for that account, and the estimated cost. After migration, you can select an account and click Reprocess. Usage events failed - Number of usage events in the request that did not process successfully Usage events successful - Number of usage events in the request that were processed successfully Usage events ready - Number of volume pricing events that are ready for bulk processing after the billing period ends (always displays zero for other pricing models)
Usage Requests section	The following tabs appear when there are events in the corresponding status. Pending Migration - Number of accounts pending migration, including the product name, the number of usage events unbilled for that account, and the estimated cost. After migration, you can select an account and click Reprocess. Usage events failed - Number of usage events in the request that did not process successfully Usage events successful - Number of usage events in the request that were processed successfully Usage events ready - Number of volume pricing events that are ready for bulk processing after the billing period ends (always displays zero for other pricing models)

Failed event errors

The Error report page provides additional information about the events that failed to process successfully and why.

Failed event errors

Error report pane	Request identifier—System-generated identifier for the request returned in a response Reprocess System Errors—Initiates reprocessing of the events on the System Error tab Download Report—Downloads a .csv file with error details Processed on—Date and time the request was processed Errors processed—The number of events that failed processing and the total number of events in the request Idempotency key—Vendor- or marketplace-assigned request identifier
Error type tabs	The following tabs display events that failed due to the corresponding error type. The number that appears next to the tab name is the number of events that failed due to the error type (and appear on the tab). System errors tab—Events that failed typically because of intermittent system failures during processing. See Fix metered usage errors. Data errors tab—Events that failed because of bad usage data. See Fix metered usage errors.
System errors tab	Event details—Date and time the request that the event is in was last submitted Request identifier—System-generated identifier for the request returned in a response Error type and Error description—Descriptions of what caused the processing failure
Data errors tab	Event details—Date and time the request that the event is in was last submitted Request identifier—System-generated identifier for the request returned in a response Error type and Error description—Descriptions of what caused the processing failure. For example: Reader not found with submitted Reader ID. Submit a different Reader ID, or configure a new reader and then submit its Reader ID. Pricing plan not found for subscription ID.