Identify Inventory Failed Events

Navigate to the Sources Dashboard.

Monitor the Total Failures card.

The Total Failures card value reflects the aggregated Metrics data:

• Events with `FAILED` and `NO_MATCH` statuses;
• Of the Inventory domain Entity types: `INVENTORY_CATALOGUE`, `INVENTORY_POSITION`, `INVENTORY_QUANTITY`, `VIRTUAL_CATALOGUE`, `VIRTUAL_POSITION`, and `BATCH`;
• Excluding data with `internal` source label.

For more details, check the Labels section of the Metrics usage for Platform Observability.

Tip

Use the Page Filter Select dropdown to set a period for the failure number aggregation.

Customize the filter periods with How to configure Page Filter Select via Manifest. 

Click the Total Failures card link, which will redirect to the Events page.

 The Events Search Results are pre-filtered with:

• Event status: `FAILED` & `NO_MATCH`;
• Root entity type: `INVENTORY_CATALOGUE` & `VIRTUAL_CATALOGUE`.

Tip

Use available filters with multi-select input to narrow the Events Search Results if needed. 

For example:

Apply the Category filter with `EXCEPTION` & `ERROR` values selected to filter out the events of any other category.

Click the SEARCH button to apply the filters selected to the Events Search Results.

Inspect the Events Search Results table.

Click the Event column value link to open the Event Details Drawer. Inspect the DETAILS and CONTEXT sections.

Scroll down to the Event Details Drawer BODY section to inspect the attributes providing the necessary information for the problem understanding and remediation, like:

• error `code` (available for `FAILED` events only);
• error `message`;
• `lastRuleSet`;
• `lastRule`;
• `entityStatus` (available for `NO_MATCH` events only);
• `closeMatches` (available for `NO_MATCH` events only).

Failed Events Identification is an initial part of the Inventory Processing monitoring to enable users to identify the specific Inventory Events that have failed and provide visibility into why those events have failed. The following example for Inventory Update (via the customer’s request based on Point Of Sale (POS) data) is intended to serve as a reference for the Inventory Failed Events Identification process.

1. The current state of the Inventory Stock-On-Hand is 25 pcs:

2. Current state of the recent (last 30 min) Inventory Updates:

3. Incorrect Inventory Update customer’s request based on Point Of Sale (POS) data is sent.

1{
2    "retailerId": "3353",
3    "entityRef": "DEFAULT:33533",
4    "name": "InventoryChanged",
5    "entityType": "INVENTORY_CATALOGUE",
6    "rootEntityType": "INVENTORY_CATALOGUE",
7    "rootEntityRef": "DEFAULT:33533",
8    "entitySubtype": "DEFAULT",
9    "type": "NORMAL",
10    "source": "POS",
11    "attributes": {
12        "inventoryPosition": {
13            "retailerId": "3353",
14            "locationRef": "F_1686296685026",
15            "productRef": "AH8050-F_1686296685026-96",
16            "qty": "10"
17        }
18    }
19}

4. The Inventory Update Failure occurred is displayed on the Sources Dashboard:

Warning

The state of the Inventory Stock-On-Hand remains unchanged (25 pcs) because of the Inventory Update failure:

5. The user is redirected to the pre-filtered Events page on Total Failures link click:

6. The Event Details Drawer is opened on Event column link click:

7. Fixed POS Inventory Update customer’s request is sent.

1{
2    "retailerId": "3353",
3    "entityRef": "DEFAULT:3353",
4    "name": "InventoryChanged",
5    "entityType": "INVENTORY_CATALOGUE",
6    "rootEntityType": "INVENTORY_CATALOGUE",
7    "rootEntityRef": "DEFAULT:3353",
8    "entitySubtype": "DEFAULT",
9    "type": "NORMAL",
10    "source": "POS",
11    "attributes": {
12        "inventoryPosition": {
13            "retailerId": "3353",
14            "locationRef": "F_1686296685026",
15            "productRef": "AH8050-F_1686296685026-96",
16            "qty": "10"
17        }
18    }
19}

8. The Inventory Update is reflected on the Sources Dashboard:

9. The Inventory Stock-On-Hand is successfully updated to 10 pcs: