Ordering Workers

By default, the reservation of Workers in a given TaskQueue is ordered by duration a Worker is unoccupied. Without an order_by expression, the Worker who has waited the longest without a Task will be the first reserved. An order_by expression allows you to designate an ordering for the Workers of a given TaskQueue based upon comparison of Workers' attributes.

The main building block of an order_by expression is an order_by clause, which is composed of:

1. an integer value in a Worker's JSON Attributes, nested or otherwise, and
2. a direction for ordering, with "ASC" representing ascending and "DESC" representing descending.

An order_by expression may be composed of any number of order_by clauses. If several Workers have the same resolved value for the first order_by criterion, the second order_by clause will break the tie by comparing the next attribute. For example, let's think about a Workspace with the following:

• TaskQueue with order_by expression "worker.finance ASC, worker.support ASC"
• Worker Alice, with attributes {finance = 10, support = 8}
• Worker Bob, with attributes {finance = 10, support = 5}

Alice and Bob are first compared using the first order_by clause, "worker.finance_level ASC", which results in a tie because their finance attributes are equal. To break the tie, the two Workers are next compared using the next order_by clause, "worker.support_level ASC". Bob's support level, 5, is less than Alice's support level, and the sort direction is ascending. When a new Task is created and enters this TaskQueue, the workers are ordered {Bob, Alice}, and Bob is reserved to handle the new Task.

What happens if a worker doesn't have a particular skill? Workers without a given skill are ordered after those that have a skill when there is a tie, regardless of whether "ASC" or "DESC" sort direction is selected. For example, given a Workspace containing:

• TaskQueue with order_by expression "worker.finance ASC, worker.support ASC"
• Worker Alice, with attributes {finance = 10, support = 8}
• Worker Bob, with attributes {finance = 10}

Alice and Bob are first compared using the first order_by clause, "worker.finance_level ASC", which results in a tie because their finance attributes are equal. To break the tie, the two Workers are next compared using the next order_by clause, "worker.support_level ASC". Bob does not have the support attribute and will therefore appear in the queue after Alice. When a new Task is created and enters this TaskQueue, the workers are ordered {Alice, Bob}, and Alice is reserved to handle the new Task.

If ordering is attempted on a non-integer attribute, then the expression is ignored.

For workers that are equal, for all supplied ordering clauses, the longest time since last task assignment is used as a final ordering condition.

1
{
2
   "task_routing":{
3
      "filters":[
4
         {
5
            "filter_friendly_name":"Sales filter",
6
            "expression":"type == 'Sales'",
7
            "targets":[
8
               {
9
                  "expression":"task.subSection = worker.specializedSubField",
10
                  "order_by":"worker.english_level ASC",
11
                  "priority":"1",
12
                  "queue":"WQ3935a4f744a241c1356c09310c2398e6"
13
               },
14
               {
15
                  "priority":"1",
16
                  "queue":"WQ787b271950e0f7687ec432221e672ffa"
17
               }
18
            ]
19
         }
20
      ]
21
   }
22
}