# The Flow Designer failure code vocabularies

Canonical: https://warmtransfer.net/knowledge/wxcc-flow-activity-failure-codes

Last verified: 2026-09-15

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](https://warmtransfer.net/knowledge/webex-cc-flow-error-paths)
* [The Webex Contact Center Flow Designer activity set](https://warmtransfer.net/knowledge/wxcc-flow-designer-activities)

## Applicability

Applies to: Cisco Webex Contact Center. Sources checked 2026-09-15.

## What remains uncertain

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

## Sources

[^1]: The HTTP Request response timeout and retry count are each described as accepting any unlimited value. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, HTTP Request activity. Checked 2026-09-15.
[^2]: The failure branch of the queue information activity is described as triggering when an interface fails or returns invalid values rather than in terms of the activity's own failure codes. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Get Queue Info activity. Checked 2026-09-15.
[^3]: The queue information activities return minus one as an expected value rather than as an error when a figure does not apply. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Get Queue Info and Advanced Queue Information activities. Checked 2026-09-15.
[^4]: Cisco states that a tenant may not see the undefined error node at all and must contact support to have the feature enabled. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Configure error handling. Checked 2026-09-15.
[^5]: The HTTP Request activity publishes no failure code variable no failure branch and no undefined error node and a flow can only test the returned status code by hand. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, HTTP Request activity and Configure error handling. Checked 2026-09-15.
[^6]: No sentence in the article relates the generic undefined error node to a failure code variable: the phrase error branch occurs 0 times and failure branch once without defining what the branch carries. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, counted against the rendered article. Checked 2026-09-15.
[^7]: The HTTP Request retry setting applies when the status code is in the 500 range so a rate-limit response or a connection timeout is not retried. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, HTTP Request activity, Number of Retries. Checked 2026-09-15.
[^8]: A Flow Designer failure code integer means different things in different activities: code 3 is feature not enabled insufficient data invalid wait time agent not logged in no answer and invalid queue depending on which activity set it. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, the 10 runtime failure code tables compared by code number. Checked 2026-09-15.
[^9]: Four failure names carry different code numbers in different activities: invalid queue is 5 4 4 3 and 3 across 5 activities system error is 1 in one activity and 6 in 5 others feature not enabled is 3 3 4 and 5 and invalid operation for interaction state is 12 and 8. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, the 10 runtime failure code tables compared by failure name. Checked 2026-09-15.
[^10]: The article publishes 10 runtime failure code tables holding 57 codes in total: 6 for advanced queue information 3 for escalate call distribution group 4 for get queue info 13 for queue contact 8 for queue to agent 2 for set contact priority 5 for bridged transfer 6 for callback 7 for record and 3 for schedule callback. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, the tables whose header row names a failure code or an error code. Checked 2026-09-15.
[^11]: Two of the 7 record activity error codes are published with an empty description column so a flow comparing the error code against a name has nothing to compare for them (field report). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Record activity error codes. Checked 2026-09-15.
[^12]: An invalid expression surfaces either as design-time error code FC1009 or as a system error during execution of the Set Variable activity and the article never relates the two. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Understand error codes and the global error handler. Checked 2026-09-15.