How to Manage System Queues [Guide]
Last updated: October 16, 2026
Queues in techOMS provide an easy-to-use page to monitor automated background tasks, helping you track system operations without needing complex technical tools.
This guide covers the universal system pattern for navigating and managing system queues.
What Is a Queue?
The queue system in techOMS acts as a window into the operations running behind the scenes. It groups together automated tasks—such as sending data to a channel or applying an automatic update—so you can easily check that everything is running smoothly and resolve issues when needed.
Sales Order Queue
The Sales Order Queue manages specific background tasks that determine how a Sales Order moves toward fulfillment. For example, it handles automated updates created by Virtual Allocation and Order Holds.
The Scheduled On column shows when a queue task is scheduled for processing. For hold-related tasks, this timestamp can represent when the hold timer expires. Do not interpret Scheduled On as a physical shipping schedule, shipment cancellation confirmation, or guaranteed completion time.
The following table describes the primary Action Types you can encounter in this queue:
Action Type | Description |
|---|---|
Download Order Update | Automatically retrieves the latest changes or revisions from the sales channel to keep techOMS synchronized. |
Release Hold and Edit | Cancels any existing shipments, releases protected inventory, and moves the order back to Draft for manual adjustments. |
Release Hold and Send | Ends the hold period and commands the system to proceed with physical allocation and fulfillment. |
Edit Order | Processes applicable shipment cancellations and returns an eligible Sales Order to Draft through background processing. For the complete workflow and expected outcomes, refer to 📄 How to Edit a Sales Order and Return It to Draft [Step-by-Step Guide]. |
For detailed conceptual information about how holds work, why they are used, and how they protect inventory, refer to 📄 Understanding Sales Order Holds and Virtual Allocation [Information].
Using the Queue
Although system queues in techOMS follow a similar interface pattern, the available fields, statuses, filters, and management actions can vary depending on the queue you are viewing. The following instructions describe the shared workflow where the corresponding controls are available.
How to Access a Queue
Click Queue from the left-hand navigation menu under the desired section.

The selected queue grid is now active and displays the available pending and historical automated tasks. You can continue by reviewing the displayed information or filtering the queue.
What Is the Displayed Information?
The queue interface uses a standard table layout designed for high visibility. The exact columns depend on the queue you are viewing. In the Sales Orders Queue, you can use the following information to monitor a task:

ID: The unique internal identifier for the specific queue task.
Origin: The source of the task, such as a specific Sales Order or Fulfillment Channel.
Action Type: The specific operation being performed. Refer to the corresponding subsection in What Is a Queue? for examples.
Status: The current state of the background task. Depending on the operation, you can encounter statuses such as Scheduled, Processing, Failed, or Completed. A queue status describes the task itself and does not replace the current status of the associated Sales Order.
Scheduled On: The timestamp associated with when the queue task is scheduled for processing. Its specific meaning can depend on the Action Type.
Attempt: For Sales Orders Queue tasks, this field shows the processing attempt associated with the queue item and can change as background processing retries an operation.
After reviewing the task information, you can filter the queue to locate a specific entry or open an entry for additional details.
How to Filter Queue Entries
There are three primary ways to locate specific tasks within a Queue:

Search Bar: Use the search field at the top of the grid to find entries by their ID, or any part of the source and action payload.
Status Dropdown: Use the dropdown next to the search bar to filter tasks by their current Status, such as displaying only Failed tasks.
Advanced Filter: Click the Advanced Filter icon to filter by additional properties, such as specific Action Types.
The options inside the Action Type filter automatically change depending on the queue you are viewing. For more information about what these actions do, review the corresponding subsection in What Is a Queue?.
After applying your filters, use the resulting queue entries to review a specific task or, where supported, manage a failed operation.
How to View Task Details
If you need to investigate a specific automated task—especially one that has failed—you can access its technical details by clicking its ID.

This opens a detail dialog that displays the underlying task data, helping you understand what the system attempted to process.

A Completed queue task also does not replace verification of the Sales Order's current status.
After reviewing the task details, close the dialog and continue monitoring the queue or use an available management action when appropriate.
How to Reprocess
The queue interface includes Reprocess for failed operations that support manual reprocessing. A Failed status by itself does not guarantee that the task can be manually reprocessed.
Edit Order does not support Reprocess. Edit Order can perform its own automatic retry behavior while background processing is active, but those automatic attempts are separate from the manual Reprocess action. Do not use this procedure as a recovery workflow for a failed Edit Order task.
For an Action Type that supports Reprocess, use the following existing procedure:
Locate the Failed task within the queue grid.
Select the checkbox next to one or multiple failed queue items.
Press Reprocess to command the system to retry the selected supported operation.

The selected supported queue items are submitted for another processing attempt, and their Status updates according to the new result. If Reprocess is not supported for the Action Type you are investigating, follow the workflow or support guidance applicable to that operation instead.