Twilio TaskRouter has default limits on certain resources, configuration parameters, and endpoints. If you are running into these limits, please reach out to our support team. We're happy to help work with you to increase some of these limits or help optimize how you use TaskRouter.
Please note that Twilio Flex only supports a single TaskRouter Workspace within a Flex Project. While you may create additional Workspaces on a Flex Project, Twilio Flex will only recognise the TaskRouter Workspace provisioned upon Project creation.
|Workflows per Workspace||The maximum number of Workflows that you can create within an individual Workspace.||1,000|
|Registered Workers per Workspace||The maximum number of registered Workers that you can create within an individual Workspace.||15,000|
|Concurrent Workers per Workspace||The maximum number of Workers that can be online concurrently within an individual Workspace.||7,500|
|Activites per Workspace||The maximum number of Activities you can create within an individual Workspace.||100|
|TaskQueues per Workspace||The maximum number of TaskQueues you can create within an individual Workspace.||5,000|
|Tasks per Workspace||
The maximum number of Tasks in any state that can exist on an individual Workspace. Please note that completed and cancelled tasks are removed after 15 minutes.
|TaskChannels per Workspace||The maximum number of TaskChannels you can create within an individual Workspace. This limit is inclusive of the default TaskChannel.||15|
|Workspaces per Project||The maximum number of Workspaces that you can create on an individual non-Flex project. Please note that Twilio Flex only supports a single workspace.||5,000|
|Channel Capacity per Worker||The maximum number of Tasks that can be assigned to a worker on a given TaskChannel.||50|
The limits on JSON attributes include whitespace. You save a few bytes by using a JSON minifier and creating/updating the Resource through the REST API.
|Workerの属性||The maximum size of the JSON string used for defining Worker attributes.||4096 bytes|
|Taskの属性||The maximum size of the JSON string used for defining Task attributes.||4096 bytes|
|Workflow Configuration||The maximum size of the JSON string used to define a Workflow.||16777215 bytes (1MB)|
|Task Timeout (Pending and Reserved Tasks)||The maximum amount of time a Task can exist in a pending or reserved state before timing out (task.timeout) and being cancelled.||1209600 seconds (2 weeks)|
|Task Timeout (Assigned Tasks)||The maximum amount of time a Task can stay assigned to a Worker before being deleted by the system (task.system-deleted).||86400 seconds (24 hours)|
|Max Reserved Workers||The maximum number of Workers that can simultaneously be offered a reservation for a Task in a TaskQueue with Multi-Reservation enabled.||50|
If a resource or method is not documented below, it is not rate limited. For TaskRouter, Twilio's REST API has a default limit of 100 max concurrent connections.
All endpoints below are prefixed by
/Workspaces/WSxxx/, with the exception of the Workspace endpoints. Rate Limits are stated in requests per second.
||GET||List all Workspaces within a Project||170|
||削除||Delete an individual Workspace||5|
||GET||List all Activities within a Workspace||150|
Fetch all Tasks within a Workspace
Fetch specific Tasks within a Workspace
||POST||Update an individual Task||50|
||POST||Update an individual Reservation||70|
||GET||List all TaskChannels within a Workspace||10|
||POST||Create a new TaskChannel||1|
||削除||Delete an individual TaskChannel||1|
||GET||List all TaskQueues within a Workspace||200|
||POST||Create a new TaskQueue||47|
||GET||Fetch an individual TaskQueue||13|
||POST||Update an individual TaskQueue||5|
||削除||Delete an individual TaskQueue||5|
||GET||List all Workers within a Workspace||240|
||POST||Update an individual Worker||60|
||GET||List all Workflows within a Workspace||10|
||POST||Update an individual Workflow||10|
|Reservations per Task||Number of times a Task can be reserved before being cancelled||1,000|
|Rejected Reservations||Number of Reservations for a Task that can be rejected before the Task is cancelled||10|
|Worker Statistics Endpoint Cap||Worker Statistics REST API endpoints are not accessible by default if you have over these many Workers in your Workspace.||100|
|Waiting Voice Calls per TaskRouter Workflow||Every TaskRouter workflow that handles voice calls has a Programmable Voice queue under the hood. This refers to the default size of that queue.||100 (max 5000)|
The limit for the number of waiting voice calls is set on a per-workflow basis and can be updated through our REST API or by using Twilio CLI and the steps below.
Find the workflow sid for the TaskRouter workflow that you are running into queue limit issues with, either through console or by running the following cli command.
Find the queue sid that matches your queue by running the following cli command. The
friendlyName for the queue you are looking for will be the workflow sid you grabbed in step 1.
Update the max size of the queue using the following cli command. The
max-size property can be an integer between 0 and 5000.
誰しもが一度は考える「コーディングって難しい」。そんな時は、お問い合わせフォームから質問してください。 または、Stack Overflow でTwilioタグのついた情報から欲しいものを探してみましょう。