Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

14232: Dial->Conference: Invalid Priority


ERROR: 14232

error-14232 page anchor
TASKROUTER
ERROR

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

possible-causes page anchor
  • 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.
  • 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

additional-resources page anchor