Error path behaviour across Flow Designer activities
Verified 2026-09-15 · 18 claims · sources tier 2 · 2 disputed
Also known as failure code, no-input timeout, undefined error.
Flow Designer activities present failure conditions through dedicated branches, generic undefined error nodes, and failure variables 1611. Only 6 activities carry error branches beyond the generic undefined error node: menu, collect digits, virtual agent, virtual agent version 2, queue to agent, and cryptographic hash 16.
Activity error branches and variables
The named branches on the menu and collect digits activities are a no-input timeout and an unmatched entry 13. For the virtual agent activity, the error code variable takes 4 values: no error, maximum no input, termination character without input, and system error 17. Most activities that describe failure carry the detail in a failure code and a failure description variable rather than in a branch 11.
Flow termination and activity documentation
Cisco warns that the End Flow activity should not be used in an interactive voice response flow, because doing so may result in dead air and the call may not disconnect 10. In the field, a table headed as GoTo activity error codes contains output variable descriptions rather than failure codes 12.
Documentation discrepancies
Sources disagree on the error path for the Parse activity: the Parse activity's own section describes an undefined error path, while the error handling section lists Parse among 4 activities that lack one 14. Sources disagree on publish rules as well, as the article gives 2 incompatible statements about whether a flow missing an error path can be published 15.
See also
See also The Webex Contact Center Flow Designer activity set. See also The Flow Designer activity catalogue. See also Webex Contact Center Flow Designer architecture.
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
Sources disagree on whether a flow missing an error path can be published 15. How an interactive voice response flow should end when End Flow is unsafe there is not covered by any claim in this article. The values each activity's failure code variable can take are not covered by any claim in this article.
See also
Part of
- The Webex Contact Center Flow Designer activity set — The error surface of the catalogue read in one pass
Related to
- The Flow Designer activity cataloguestub — Carries the Parse contradiction as a disputed claim
- What an event flow can do — Where a flow ending leaves a contact
Referenced by
- How a business hours configuration binds to a routing flow — Error path behaviour observed on this activity
- The Flow Designer failure code vocabularies — What the failure variable can say
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | Get Queue Info is the only contact handling activity with 3 named outcome branches: Success Insufficient Information Flow and Failure. Build and manage flows with Flow Designer · Flow Designer, Get Queue Info activity | fact | 0.90 | 2026-09-15 |
| 2 | The activity set uses at least 5 different label conventions for the same idea of an outcome: Success and Failure on one activity onSuccess and onError on another Handled and Escalated and Error on a third Errored on its successor and True and False on the branching activities. Build and manage flows with Flow Designer · Flow Designer, activity output ports across the catalogue | field-pattern | 0.90 | 2026-09-15 |
| 3 | Cisco states that a tenant may not see the undefined error node at all and must contact support to have the feature enabled. Build and manage flows with Flow Designer · Flow Designer, Configure error handling | fact | 0.90 | 2026-09-15 |
| 4 | 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. Build and manage flows with Flow Designer · Flow Designer, HTTP Request activity and Configure error handling | fact | 0.90 | 2026-09-15 |
| 5 | 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. Build and manage flows with Flow Designer · Flow Designer, counted against the rendered article | fact | 0.90 | 2026-09-15 |
| 6 | 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. Build and manage flows with Flow Designer · Flow Designer, the 10 runtime failure code tables compared by code number | fact | 0.90 | 2026-09-15 |
| 7 | Four activities have no undefined error node at all: Start Flow End Flow HTTP Request and Parse. Build and manage flows with Flow Designer · Flow Designer, Configure error handling | fact | 0.90 | 2026-09-15 |
| 8 | Cisco instructs a reader who cannot see the undefined error node in any activity to contact support to have the feature enabled. Build and manage flows with Flow Designer · Flow Designer, Configure error handling | fact | 0.90 | 2026-09-15 |
| 9 | An activity with no error path connected falls through to the global error handler on the event flow canvas and a flow with neither ends when an error occurs. Build and manage flows with Flow Designer · Flow Designer, Configure error handling | fact | 0.90 | 2026-09-15 |
| 10 | Cisco warns that the End Flow activity should not be used in an interactive voice response flow, because doing so may result in dead air and the call may not disconnect. Build and manage flows with Flow Designer · Flow Designer, End Flow activity | fact | 0.90 | 2026-09-15 |
| 11 | Most activities that describe failure carry the detail in a failure code and a failure description variable rather than in a branch. Build and manage flows with Flow Designer · Flow Designer, activity output variables | fact | 0.90 | 2026-09-15 |
| 12 | A table headed as GoTo activity error codes contains output variable descriptions rather than failure codes. Build and manage flows with Flow Designer · Flow Designer, GoTo activity | field-pattern | 0.90 | 2026-09-15 |
| 13 | The named branches on the menu and collect digits activities are a no-input timeout and an unmatched entry. Build and manage flows with Flow Designer · Flow Designer, Menu and Collect Digits activities | fact | 0.90 | 2026-09-15 |
| 14 | The Parse activity's own section describes an undefined error path and the error handling section lists Parse among 4 activities that lack one. Build and manage flows with Flow Designer · Flow Designer, Parse activity against Configure error handling | disputed | 0.60 | 2026-09-15 |
| 15 | The article gives 2 incompatible statements about whether a flow missing an error path can be published. Build and manage flows with Flow Designer · Flow Designer, Configure error handling and the publish validation text | disputed | 0.60 | 2026-09-15 |
| 16 | Only 6 Flow Designer activities carry error branches beyond the generic undefined error node: menu, collect digits, virtual agent, virtual agent version 2, queue to agent and cryptographic hash. Build and manage flows with Flow Designer · Flow Designer, activity error outputs | fact | 0.90 | 2026-09-15 |
| 17 | The virtual agent error code variable takes 4 values: no error, maximum no input, termination character without input, and system error. Build and manage flows with Flow Designer · Flow Designer, Virtual Agent activity error code | fact | 0.90 | 2026-09-15 |
| 18 | An expression written without its double curly braces throws a flow error and the article states this for the Condition activity only. Build and manage flows with Flow Designer · Flow Designer, Condition activity | fact | 0.90 | 2026-09-15 |
Sources
Build and manage flows with Flow Designer
Cite this page
APA
WarmTransfer. (2026, September 15). Error path behaviour across Flow Designer activities. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-flow-error-paths
BibTeX
@misc{warmtransfer-webex-cc-flow-error-paths,
title = {Error path behaviour across Flow Designer activities},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-cc-flow-error-paths},
note = {Verified 2026-09-15}
}