14240: Max concurrent Workers exceeded

You receive this error when your TaskRouter Workspace has reached the limit for concurrent active Workers. TaskRouter uses a Worker's Activity to determine whether the Worker is eligible to receive Tasks. Activities whose available value is true make the Worker eligible for task assignment.

• Your Workspace already has the maximum number of active Workers.
• Too many Workers are currently in an Activity whose available value is true.
• You created a Worker with an ActivitySid that points to an available Activity.
• You updated Workers into an available Activity and did not move them back to an unavailable Activity when they were no longer ready to receive Tasks.
• In a multitasking Workspace, Worker state does not automatically change when a Task is assigned or accepted, so Workers can remain active until your application updates them.

• Move Workers who should not receive new Tasks to an unavailable Activity such as Offline or Unavailable.
• Review your Workers and identify which ones are still active by listing Workers with filters such as Available=true, ActivitySid, or ActivityName.
• When you create a Worker, set ActivitySid to an unavailable Activity if the Worker should not become active immediately.
• If you do not pass ActivitySid when creating a Worker, use the Workspace default_activity_sid. By default, new Workers start in Offline unless you changed that setting.
• In a multitasking Workspace, explicitly update Worker Activities when your agents should stop receiving new Tasks.
• If you move a Worker to an unavailable Activity and the Worker still has pending reservations, use rejectPendingReservations when you update the Worker.

• Worker Resource
• Activity Resource
• How TaskRouter Works