The Flow Designer failure code vocabularies

Verified 2026-09-15 · 12 claims · sources tier 2

Also known as FailureCode, FailureDescription.

Flow Designer publishes runtime failure codes across specific activity tables rather than as a single platform-wide vocabulary 10. These numeric codes and failure names vary depending on which activity encounters the failure 8​9.

Runtime failure code distribution

Published documentation provides 10 runtime failure code tables containing 57 codes in total 10. These tables cover:

• Advanced queue information: 6 codes 10
• Escalate call distribution group: 3 codes 10
• Get queue info: 4 codes 10
• Queue contact: 13 codes 10
• Queue to agent: 8 codes 10
• Set contact priority: 2 codes 10
• Bridged transfer: 5 codes 10
• Callback: 6 codes 10
• Record: 7 codes 10
• Schedule callback: 3 codes 10

In the field, 2 of the 7 Record activity error codes are published with an empty description column, leaving a flow comparing the error code against a name with nothing to compare for those 2 codes 11.

Code and name collisions across activities

A Flow Designer failure code integer represents different meanings depending on the activity that set it 8. For example, code 3 represents "feature not enabled", "insufficient data", "invalid wait time", "agent not logged in", "no answer", or "invalid queue" based on the originating activity 8.

Similarly, 4 failure names map to different integer codes across activities 9:

• "Invalid queue" maps to 5, 4, 4, 3, and 3 across 5 distinct activities 9.
• "System error" maps to 1 in 1 activity and 6 in 5 other activities 9.
• "Feature not enabled" maps to 3, 3, 4, and 5 9.
• "Invalid operation for interaction state" maps to 12 and 8 9.

Error branching and HTTP Request handling

No rule relates the generic undefined error node to a failure code variable; documentation contains the phrase "error branch" 0 times and "failure branch" once without defining what the branch carries 6. Furthermore, Cisco states that a tenant may not see the undefined error node at all and must contact support to have the feature enabled 4.

The HTTP Request activity defines no failure code variable, no failure branch, and no undefined error node, requiring a flow to evaluate returned status codes manually 5. Retry settings for the HTTP Request activity apply only when the status code falls in the 500 range, meaning connection timeouts and rate-limit responses do not trigger retries 7.

See also

• Error path behaviour across Flow Designer activities
• The Webex Contact Center Flow Designer activity set

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-15. The deployment model is not covered by any claim in this article.

What remains uncertain

Whether a Flow Designer failure code is meant to be read per activity or globally is not covered by any claim in this article. What a failure code variable holds when an activity succeeds is not covered by any claim in this article. What a flow can do when an HTTP Request returns no status code at all is not covered by any claim in this article. The names of the 2 record activity error codes published with an empty description are not covered by any claim in this article.

WarmTransfer. (2026, September 15). The Flow Designer failure code vocabularies. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-flow-activity-failure-codes

@misc{warmtransfer-wxcc-flow-activity-failure-codes,
  title  = {The Flow Designer failure code vocabularies},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-flow-activity-failure-codes},
  note   = {Verified 2026-09-15}
}