Lifecycle of a Task: Timeout Evaluation

Timeouts help create a good customer experience by ensuring that a Task never gets "stuck" in a Queue with no available workers. Timeout behaviors can be tricky to master, but once you do, they'll give you fine-grained control over the movement of your Tasks through your Workflows.

Consider the following Workflow:

The Code

{
    "task_routing": {
        "filters": [
            {
                "targets": [
                    {
                        "queue": "Q1",
                        "timeout": 10
                    },
                    {
                        "queue": "Q2",
                        "timeout": 10
                    },
                    {
                        "queue": "Q3",
                        "timeout": 10
                    },
                ],
                "expression": "1==1"
            }
        ]
    }
}

The reservation timeout is 5 seconds.

What Happens

1. Task A is created against the Workflow.
2. At t=3, a Reservation created for Task A against Q1.
3. At t=8, the reservation times out for Task A.
4. Task A re-evaluates and maps to Q2.

The Queue timeout is now the sum of Q1 and Q2 timeouts: 20. The target timeout for this task will happen in 12 sec, however, because it is based on the Task's current time. Unlike the Reservation Timeout (which always starts at zero), the queue timeout will be based on the current age of the Task.

Next Steps

• Review the Task State Lifecycle and how a Task moves from pending to completed
• Review the Workflow and Assignment Lifecycle and how TaskRouter finds a Worker to whom it can assign a Task
• Start configuring your own Workflows