The techOMS Statistics & Exceptions Dashboard helps you quickly identify and investigate supported processing exceptions, allowing you to take corrective action when an issue affects an order, fulfillment process, or supported channel operation.

The dashboard presents exception data in two ways, depending on the dashboard mode. This guide covers how you can investigate and handle exceptions in both modes.

Handle Processing Exceptions

To handle processing exceptions:

1. Filter the desired data in the dashboard.

The Exceptions table provides its data according to the dashboard mode:

• Organization-Level: Provides an overview of processing exceptions across your organization. Continue to the next step to drill down to the exception you want to investigate.

• Account-Level: Provides detailed processing exception data for the selected account. Continue to Step 3.

2. Click the Warning Processing value that categorizes the exception you want to investigate.

When you view the Exceptions table in Organization-Level mode, the table title displays the total number of exceptions across your organization.

To return to the previous list, click Exceptions.

3. Locate the exception you want to investigate and use the action displayed in the Actions column.

Depending on the represented Entity Type, you can see one of the following actions:

• View Orders: Opens the affected Sales Orders in a new tab.

• View Purchase Orders: Opens the affected Purchase Orders in a new tab.

• View Shipments: Opens the affected Shipments in a new tab.

• View Receipts: Opens the affected Receipts in a new tab.

• View Logs: Opens the relevant Sales Channel or Fulfillment Channel logs. Where applicable, the log view opens already scoped to the queue entries associated with the exception.

When you start from Organization-Level mode, techOMS opens the applicable destination in the relevant account context.

Exceptions Table

The Exceptions table displays the following information:

• Warning Processing: Displays the description or title of the represented processing issue.

• Entity Type: Identifies the entity or channel represented by the exception row.

• Source: Identifies the source that produced the exception.

• Account: Identifies the account associated with the exception.

• Level: Identifies the severity level of the exception.

• Count: For an entity-level exception, the value represents the distinct affected records included in the grouped exception. For a channel-operation exception, the value represents distinct queue entries and does not necessarily indicate how many Sales Orders, Purchase Orders, Shipments, or Receipts were processed by those queues.

• Actions: Displays the available navigation action based on the entity or channel represented by the exception.

Multiple current instances of the same supported processing issue can be represented by one aggregated row with its current Count.

A Warning or Error recorded in a log does not automatically create a dashboard exception. The dashboard displays supported processing exceptions captured by the applicable processing flows.

How Active Exceptions Update

The Exceptions table reflects the persisted exception state when processing completes and you refresh the dashboard.

• When the same queue entry is retried and fails again, techOMS updates or replaces its active exception instead of accumulating obsolete duplicates for that queue entry.

• When the same queue entry is retried successfully, its corresponding active exception is cleared after the updated state is reflected on the dashboard.

• When processing is started through Reprocess, a different queue entry is created. Successfully processing that new entry does not automatically clear the exception associated with the original failed queue entry.

Historical processing information remains available in the applicable channel logs, even after an active dashboard exception is cleared. Use the dashboard for current exception investigation and the applicable logs when you need processing history or additional diagnostic information.

Missing Product Variant

The Missing product variant workflow is a special-case exception workflow and should not be considered representative of every processing exception.

Within Step 3, if the Warning Processing message is Missing product variant, click the message to open a pop-up that displays the missing SKUs table. From this table, click View Orders to open a new tab containing the affected orders for that specific SKU.

After you identify the affected records, take the required corrective action, such as updating the applicable product details.

After completing the corrective action, return to the techOMS Statistics & Exceptions Dashboard and refresh it to verify the current exception state.