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

# 14233: Dial->Conference: Invalid Timeout

Log Level: ERROR

## Description

This error occurs when you send a Conference instruction for a TaskRouter reservation and the Timeout value is not a valid integer. For a Conference instruction, Timeout controls how long Twilio rings the phone associated with the Worker's `contact_uri` before assuming there is no answer. The default is 60 seconds and the maximum is 999 seconds.

### Possible causes

* Your application sent Timeout as a non-integer value, such as text, a decimal, or an empty value, instead of an integer number of seconds.
* Your application sent a Timeout value greater than 999 seconds for the Conference instruction.
* If you use the TaskRouter JavaScript SDK, your `reservation.conference()` call passed a `timeout` value that does not represent integer seconds.

### Possible solutions

* Send Timeout as an integer number of seconds, for example 30.
* Keep Timeout at 999 seconds or less. If you do not need a custom value, omit Timeout and use the default of 60 seconds.
* Validate and sanitize the Timeout value in your application before you send the Conference instruction or call `reservation.conference()`. Reject blank, non-numeric, and decimal values before making the request. This follows from the requirement that Timeout be an integer.

#### Additional resources

* [Task Reservation Resource](/docs/taskrouter/api/reservations)
* [TaskRouter JavaScript SDK: reservation.conference](/docs/taskrouter/js-sdk-v1/workspace/worker#reservation-conference)
* [TwiML Voice: `<Conference>`](/docs/voice/twiml/conference)