---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/14226#article
headline: "14226: TaskRouter Enqueue not supported in this realm"
url: https://www.twilio.com/docs/api/errors/14226
inLanguage: en
dateModified: 2026-06-08T11:38:30.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 14226: TaskRouter Enqueue not supported in this realm

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you use `<Enqueue>` with the `workflowSid` attribute to create a TaskRouter Task for a call in a realm or Region where that integration is not available. Twilio Regions operate in isolation, so products and features that are unavailable in the target Region do not work there.

### Possible causes

* Your TwiML response includes `<Enqueue>` with `workflowSid`, which invokes TaskRouter routing for the call.
* The call is being handled in a Twilio realm or Region where TaskRouter enqueue is not supported.
* Your application, SDK, or resource configuration is targeting a different Region than the one where the workflow was designed to run. Regional resources and feature availability can differ by Region.

### Possible solutions

* Run this call flow in a realm or Region that supports the required Voice and TaskRouter features. Verify regional availability before you deploy.
* If you must stay in the current Region, remove `workflowSid` and use standard Voice queueing with `<Enqueue>` or another supported routing pattern instead of TaskRouter enqueue.
* Review the Region and endpoint configuration used by your application and regional resources so the call is executed in the intended Region.

#### Additional resources

* [TwiML Voice: `<Enqueue>`](/docs/voice/twiml/enqueue)
* [Queueing Twilio calls with TaskRouter](/docs/taskrouter/twiml-queue-calls)
* [Regional product availability](/docs/global-infrastructure/regional-product-and-feature-availability)