What happens when a queue is finished

A finished queue is not deleted or archived. It is disabled — and that is the only change it undergoes.

Step by step

See queues that are no longer visible

1. Open the queue list — the Queue tab.
2. Above the table, on the left side of the bar, there is a button with a funnel icon. It says Active — completed queues are hidden.
3. Click it. The label changes to All, and the table shows everything.
4. The setting is stored in the page URL (hide_completed=false), so refreshing the page or sending the link to a colleague does not lose it.

Clear a queue’s history

1. Open the queue by clicking #number or its name in the table.
2. Go to the Settings tab and scroll to the bottom.
3. Find the red Danger zone card. You can see it only with the wms.queue_delete permission; without it, the card is absent.
4. Click Clear history.
5. The Confirm Queue History Deletion dialog opens. In Type DELETE to confirm, enter exactly DELETE. The button remains disabled until you do.
6. Click Delete Queue History. The queue remains, but empty; orders return to the pending state, and the message says how many products and quantity records were deleted.

Delete an entire queue

1. On the queue list, open the row menu (⋮ icon in the last column).
2. Select Delete.
3. In the Confirm Delete dialog, review the list of things that will disappear and click Delete.
4. A queue used as a scenario’s filter source cannot be deleted. A red bar appears at the bottom of the screen: Failed to delete queue: followed by a sentence beginning Queue "…" (ID: …) cannot be deleted because its auto-queue config is used as the filter source by the following queue creation scenario(s): and the scenario names. Unlink it from those scenarios and try again.

The order’s remaining trail

Warehouse statuses are appended, not overwritten, so the whole path remains on the order:

IN PROGRESS → SORTING → PACKING → PACKED

• IN PROGRESS — when it is added to the queue,
• SORTING — after it is dropped off at sorting,
• PACKING — after it is moved to a packing station,
• PACKED — after the shipping label is confirmed.

Units remain in the database with Completed status. This is warehouse history, not clutter.

Nightly disabling

Every day at 01:00, a background task checks active queues and disables those that have items and none unfinished. There are two exceptions:

• an empty queue stays active — empty is not the same as finished,
• a queue with automatic top-up enabled stays active — a permanent queue can reach zero overnight and fill up again in the morning.

Why old queues are not visible

The list opens with the filter set to Active — a single button with a funnel icon that switches between Active and All. It is this button that hides completed queues. A “completed” queue has packing items and none untouched. Turn off the filter to see everything.

Closing via a scenario

If a scenario creates queues, it can also close them itself — after a period, after the date changes, after a certain number of orders, or when the next queue is created. Note the nuance: the scenario disables automatic top-up, not the queue itself. The queue remains active; it simply stops receiving orders.

Clearing history is not deletion

These are two different operations, and confusing them has consequences.

Queue deletion cannot be undone and is recorded in the log as a warning.

A queue that is a scenario filter source cannot be deleted — you will get a denial with the queue_is_scenario_source code. Unlink it from the scenario first.

What is not available

You cannot split a queue, merge queues, or move orders between queues. The only route is remove from queue A, add to queue B. The “bulk update” action on the list, despite its name, only refreshes pick locations.