Rate this page:

Skipping Based on Worker Availability

By default when a Task is processing through a Workflow, a Task will wait in a routing step until it is matched to a Worker or until a timeout moves it to the next routing step. If there are initially no matching Workers, it may be preferable to skip to the next routing step immediately. To do this, use the Skip Timeout expression:

skip_if: workers.available == 0


The following special variables can be used to evaluate against the Activity of Workers. These variables are scoped to the Workers in the TaskQueue associated with the currently processing routing step.

Value Meaning
workers.available The number of workers in queue that are in an Available activity state
workers.unavailable The number of workers in queue that are in an Unavailable activity state
workers.WAxx The number of workers in queue that are in the activity state corresponding to WAxx, where WAxx is a valid ActivitySid

Skip Timeout will only be evaluated if a Task cannot be assigned to a Worker immediately. Also, Skip Timeout is only successful if the expression evaluates to true. Therefore, TaskRouter will only skip a routing step in a Workflow if:

  • No Reservations are immediately created when a Task enters the routing step
  • The Skip Timeout expression evaluates to true

If a Task skips a filter, it will be evaluated as if the Task didn't match the filter expression. This is important when considering your default_filter behavior because, even though they match one of the filter expressions, Tasks that skip a named filter still qualify for the default_filter.

You can read more about the behavior of the default filter in the Workflow Overview.

Skipping Based on Capacity

The variables mentioned above only relate to the Activity of Workers. In a multitasking Workspace, Tasks are only assigned to Workers if they:

  • match the rules of the routing step (i.e., are part of the selected TaskQueue and match the Workers expression)
  • are in an Available Activity
  • have capacity on the Task's channel

The expression 1==1 is useful here. Because 1==1 will always evaluate to true, it can be used to skip the routing step if no Workers are available that match the above criteria.


Example Skip Timeout expressions:

  • 1==1
  • workers.available == 0
  • workers.WAxx < 2
  • workers.WAxx < 2 OR workers.WAyy < 2

Skip Timeout expressions must evaluate to true or false, support equality and comparison, and can be compounded with AND/OR logical operators.

            "filter_friendly_name":"Sales filter",
            "expression":"type == 'Sales'",
                  "expression":"task.subSection == worker.specializedSubField",
                  "order_by":"worker.english_level ASC",
                  "skip_if": "workers.available == 0"
Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Loading Code Sample...

        Thank you for your feedback!

        Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

        Sending your feedback...
        🎉 Thank you for your feedback!
        Something went wrong. Please try again.

        Thanks for your feedback!