WarmTransfer
webex contact center · published

Webex Contact Center flow activity error paths

Verified 2026-09-15 · 7 sources · tier 2 · 1 superseded

Also known as undefined error node.

Superseded guidance: 1 source has been superseded by newer ones.

An activity in Flow Designer that has no error path connected falls through to the global error handler on the event flow canvas 7. A flow with neither an activity-level error path connected nor a global error handler ends when an error occurs 7.

Activity error nodes and classes

A total of 20 activities document the undefined error node, and 19 of those activities carry the identical boilerplate sentence describing that node 6.

WarmTransfer's reading of the sources is that error path coverage follows the activity class rather than the activity itself: the flow control class contains 3 of the 4 activities that have no error node, whereas the contact handling class holds every activity with a named outcome branch 2.

Feature enablement

Cisco instructs a reader who cannot see the undefined error node in any activity to contact support to have the feature enabled 5. WarmTransfer's reading of the sources is that a tenant without the error handling feature enabled sees no undefined error node on any activity, meaning an automated coverage check over its flows reports every activity as uncovered, and nothing within the flow distinguishes that state from a tenant that possesses the feature but has connected no error paths 3.

Applicability

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

What remains uncertain

What a contact experiences when a flow ends outside an interactive voice response flow is not covered by the sources below. Which activities are most likely to need an error path connected is not covered by the sources below.

See also

Part of

Related to

Sources

  1. 1
    The Undefined Error node (used to route undefined system errors) is not present on 4 Flow Control activities: Start Flow, End Flow, HTTP Request, and Parse.
    Build and manage flows with Flow Designer · Configure error handling · Checked 2026-09-04
  2. 2
    Error path coverage follows the activity class rather than the activity: the flow control class holds 3 of the 4 activities with no error node and the contact handling class holds every activity with a named outcome branch.inferred
    Build and manage flows with Flow Designer · Flow Designer, the activity classes compared for error outputs · Checked 2026-09-15
  3. 3
    A tenant without the error handling feature enabled sees no undefined error node on any activity, so an automated coverage check over its flows reports every activity as uncovered, and nothing in the flow distinguishes that from a tenant that has the feature and has connected no error paths.inferred
    Build and manage flows with Flow Designer · Flow Designer guide, undefined error node and the support instruction beside it · Checked 2026-09-15
  4. 4
    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 · Checked 2026-09-15
  5. 5
    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 · Checked 2026-09-15
  6. 6
    Twenty activities document the undefined error node and 19 of them carry the same boilerplate sentence describing it.
    Build and manage flows with Flow Designer · Flow Designer, counted across the activity sections of the rendered article · Checked 2026-09-15
  7. 7
    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 · Checked 2026-09-15

Documents

tier 2 current vendor documentation

Build and manage flows with Flow Designer

Cisco Systems, Inc. (Webex Help Center) · 2026-09-03 · accessed 2026-09-05

Cite this page

APA

WarmTransfer. (2026, September 15). Webex Contact Center flow activity error paths. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-flow-error-path-coverage

BibTeX

@misc{warmtransfer-wxcc-flow-error-path-coverage,
  title  = {Webex Contact Center flow activity error paths},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-flow-error-path-coverage},
  note   = {Verified 2026-09-15}
}