---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/14232#article
headline: "14232: Dial->Conference: Invalid Priority"
url: https://www.twilio.com/docs/api/errors/14232
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 14232: Dial->Conference: Invalid Priority

Log Level: ERROR

## Description

This error occurs when you provide a `priority` value for a TaskRouter conference flow and that value is not a valid integer. When you attach `priority` and `timeout` to a Task, both values must be valid integers. TaskRouter uses priority to determine task assignment order, so Twilio rejects values that cannot be parsed as an integer.

### Possible causes

* The `priority` value contains letters, spaces, punctuation, or other non-numeric characters.
* The `priority` value is a decimal, boolean, empty string, or `null` instead of a whole number.
* Your application generates TwiML or a TaskRouter request dynamically and inserts an invalid `priority` value into the final payload.
* A variable or template substitution step converts an expected integer into a non-integer string before the Task is created.

### Possible solutions

* Set `priority` to a whole-number integer such as `5`.
* Validate and normalize any dynamic input before sending it as `priority`.
* Inspect the final TwiML or TaskRouter request payload and confirm `priority` contains only a valid integer value.
* If you do not need custom task prioritization, remove the invalid value and use the default Task priority.

#### Additional resources

* [Queueing Twilio calls with TaskRouter](/docs/taskrouter/twiml-queue-calls)
* [Task Resource](/docs/taskrouter/api/task)
* [Task Reservation Resource](/docs/taskrouter/api/reservations)