WarmTransfer
webex contact center · published

Troubleshooting Webex Contact Center flows

Verified 2026-09-25 · 50 sources · tier 2–4

In Webex Contact Center Flow Designer, the flow validation toggle is located on the right of the footer pane and is off by default, and turning it on initiates backend validation to reveal errors 48. A flow cannot be published until validation is turned on and every validation error is resolved, leaving the Publish button disabled otherwise 27.

Validation and publishing

Since the 24 April 2026 Flow Designer update, attaching an End activity to a port is a recommendation instead of a mandatory validation rule, eliminating a class of validation errors that previously blocked publishing 11. Flow Designer flows support Dev, Test, and Live version labels for development, staging, and production environments, and the label that an incoming contact runs is selected at the Entry Point 49. The Flow Designer documentation states that there is currently no version control feature, meaning the flow version number merely reflects the total number of times the flow has been published 25.

On 27 April 2026, Flow Designer received a modernized canvas featuring dark mode, updated activity groupings, and improved search, which means screenshots and menu paths in older documentation may differ from the active interface 2. The start activity formerly named NewPhoneContact is being renamed NewContact as it transitions to an omnichannel start node; Cisco states that digital channels and work items will be incorporated into it later 24. From July 2026, administrators and developers can programmatically author, validate, publish, export, and lock flows using the public Flow schema and Flow V2 APIs on the Webex Contact Center developer portal 20.

Error paths and queue diagnostics

Many Flow Designer activities provide an "Undefined Error" output path that flow developers can wire up to manage system errors encountered during flow execution 47. Event flows are optional and execute asynchronously to the main flow, firing at unpredictable moments such as agent acceptance; each event flow requires its own start and end nodes and cannot share activities with other flows 14.

The Queue Contact activity exposes several output variables: QueueId (the queue where the contact was placed), FailureCode, and FailureDescription (populated when queuing fails) 30. When troubleshooting, WarmTransfer's reading of the sources is that FailureCode must be checked against the table for the specific activity that generated it, because Queue Contact and Advanced Queue Information maintain distinct numbering systems 15. Queue Contact reports the following specific failure codes: 33

  • Code 1 (INVALID_REQUEST): Parameters in the activity are invalid 33.
  • Code 2 (INVALID_ROUTING_STRATEGY): The selected routing strategy is invalid 29.
  • Code 3 (INVALID_WAIT_TIME): The defined wait time is invalid 33.
  • Code 4 (INVALID_QUEUE): The activity specifies an invalid queue 29.
  • Code 6 (SYSTEM_ERROR): An internal platform error occurred 33.
  • Code 7 (VTEAM_TRANSITION_LIMIT_REACHED): The contact reached the maximum permitted transfers between queues 34.
  • Code 8 (OWNER_ASSIGNED_TO_INTERACTION): The contact is already assigned to an agent 32.
  • Code 9 (INVALID_SKILL_NAME), Code 10 (INVALID_SKILL_CONDITION), and Code 11 (INVALID_SKILL_VALUE): Skills-based queuing request parameters contain invalid names, conditions, or values 31.
  • Code 12 (INVALID_OPERATION_FOR_INTERACTION_STATE): The contact is in an unqueueable state, such as an interaction that has already terminated 32.
  • Code 13 (WEIGHT_NOT_SUPPORTED_FOR_SKILL_TYPE): A weight was configured on a skill requirement that is not a Proficiency type 44.
  • Code 14 (INVALID_SKILL_WEIGHT): Skill weights were not defined as integers between 1 and 1000 44.

Beyond code-level validation, structural queuing limits apply: an interaction can carry at most 10 skill requirements, and a queue supports at most 20 Call Distribution Groups and 250 teams across all its groups 35.

Activity self-loop limits

Flow Designer enforces execution limits on the number of times an activity can loop back onto itself: 41

Activity Self-loop limit
Disconnect Contact 0 39
Upload Audio 3 40
Callback, Blind Transfer, Schedule Callback, Record, Recording Control, Call Progress Analysis, FeedbackV2 10 42
Start Media Stream 20 40
Virtual Agent, Virtual Agent V2 50 40
Bridged Transfer 75 42
Queue Contact, Queue To Agent 100 41
Menu, CollectDigit, Set Caller ID, Set Contact Priority 100 40
Escalate Call Distribution Group 750 38
Advanced Queue Information 1500 38

HTTP Request activity troubleshooting

Cisco TAC advises testing API endpoints outside of Flow Designer—such as in Postman—to verify a 200 OK response before configuring the HTTP Request activity 45. Cisco also recommends placing a Case activity directly after the HTTP Request activity to evaluate the returned httpStatusCode variable, verifying successful responses such as 200 OK and handling specific target API error codes 3. Outbound API requests initiated from Flow Designer are rate limited, and Cisco recommends designing flows to gracefully catch and process HTTP 429 status codes 17.

The HTTP Request activity includes a "Use Authenticated Endpoint" toggle: when enabled, the activity relies on a connector set up in Control Hub, supplying only the endpoint path while the connector provides the base URL and OAuth authentication 21. When configured with a connector, the connector's Resource Domain holds strictly the host component of the URL and the HTTP Request activity contains the path; mixing the domain into the path or the path into the domain is a misconfiguration 9. Webex Contact Center API connectors can be provisioned with Read-Only access (restricted to GET requests) or Read-Write access (required for POST, PUT, and update requests) 8. WarmTransfer's reading of the sources is that POST or PUT requests routed through a Read-Only connector are likely to fail authorization, indicating connector permissions should be reviewed if write actions fail while read operations succeed 37.

To execute requests with Basic authentication without a connector, the "Use Authenticated Endpoint" toggle must be turned off, the complete URL entered directly in the activity, and an Authorization header added containing Basic followed by the Base64-encoded username:password string 22.

Logging and observability

Since June 2026 Flow Designer provides a 'flow:error' webhook that sends observability events when a flow hits an error, so teams can monitor failed flow executions in near real time 18. Cisco names Splunk as an example of an external analytics platform that can take flow:error webhook events 19. In December 2025, Cisco announced Enhanced Flow Debugging for Flow Designer, describing log decryption and search with granular controls and filters while keeping sensitive data protected 12.

To isolate interactions, the contact session ID for a Webex Contact Center call can be found in the Real-Time report drill-down, the historical CSR report filtered by ANI or DNIS, the Agent Desktop URL during an active call, or the agent problem report by searching for Interaction ID: 43.

In Webex Connect digital flows, execution trace details are gathered only when Descriptive Logs is enabled in flow settings; Cisco recommends disabling this in production because continuous logging can degrade tenant performance 6. In Webex Connect Flow Debug, high-level summary logs do not hold PII and remain unencrypted, whereas detailed node execution logs may contain PII and are encrypted, requiring explicit client administrator permissions to decrypt 7. The Webex Connect Flow Debug panel shows the 10 most recent flow runs, logs usually appear about 2 minutes after execution, and executions can be filtered by transaction ID and date within the latest 30 days, after which the Debug Console must be used 5. A 2021 Cisco lab for Webex Connect digital flows asks that the create-task response ID and the transaction ID be supplied when opening a TAC case about a flow 4. WarmTransfer's reading of the sources is that while the procedure of turning on descriptive logs, opening the debug pane, decrypting logs, and clicking the transaction ID is documented for Webex Connect flows, no current Cisco document confirms that the same steps apply to Webex Contact Center Flow Designer voice flows 10.

See also

See also Webex Contact Center Flow Designer architecture. See also Webex Contact Center queues teams and routing strategies. See also Webex Contact Center APIs and webhooks. See also Webex Contact Center system limits reference. See also Webex Connect digital channel flow orchestration.

Applicability

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

What remains uncertain

The Flow Designer Debug flows section procedure and trace retention are not covered by the sources below. HTTP Request activity settings, timeout, retries, output variables, and error path semantics are not covered by the sources below. Whether descriptive logs and decrypt logs apply to Webex Contact Center Flow Designer voice flows is not covered by the sources below. OnGlobalError trigger wording and error variables exposed to the event flow are not covered by the sources below. The flow:error webhook payload schema and subscription steps are not covered by the sources below. The Flow V2 API validate endpoint error output format is not covered by the sources below. The numeric rate limit for API calls from Flow Designer is not covered by the sources below. Behaviour when a self-loop limit is reached, including whether it exits via a global error path, is not covered by the sources below.

See also

Referenced by

Sources

  1. 1
    The Advanced Queue Information activity has its own failure-code table running from 1 (INVALID_REQUEST) to 48 (UNSUPPORTED_FLOW_ACTIVITY), including QUEUE_NOT_FOUND, FEATURE_NOT_ENABLED and DATABASE_OPERATION_FAILURE.
    Build and manage flows with Flow Designer · section 'Advanced Queue Information' > failure code table · Checked 2026-09-25
  2. 2
    On 27 April 2026 Flow Designer received a modernised canvas with dark mode and reorganised activity grouping with improved search, so screenshots and menu paths in older guides may not match the current UI.
    What's new for administrators in Webex Contact Center · entry dated April 27, 2026 · Checked 2026-09-25
  3. 3
    Cisco guidance is to put a Case activity after the HTTP Request activity and branch on the returned HTTP status code (httpStatusCode), for example to check for 200 OK and to handle each error code the target API defines.
    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · section 'Verify' · Checked 2026-09-25
  4. 4
    A 2021 Cisco lab for Webex Connect digital flows asks that the create-task response ID and the transaction ID be supplied when opening a TAC case about a flow.
    Lab 2(c): Flow Debugging Flows · closing note after step 5 · Checked 2026-09-25
  5. 5
    The Webex Connect Flow Debug panel shows the 10 most recent flow runs; logs usually appear about two minutes after execution; executions can be filtered by transaction ID and date within the latest 30 days; older transactions need the Debug Console.
    Flow Debug · opening Flow Debug and search/filter sections · Checked 2026-09-25
  6. 6
    In Webex Connect flows, node execution details are captured only when Descriptive Logs is turned on in flow settings, and Cisco recommends using it only during initial set-up and troubleshooting because leaving it on in production can degrade tenant performance.
    Flow Debug · Descriptive Logs section · Checked 2026-09-25
  7. 7
    In Webex Connect Flow Debug, summary logs contain no PII and are not encrypted, while node execution details may contain PII and are encrypted; only users the client admin has authorised can decrypt them.
    Flow Debug · encryption and permissions section · Checked 2026-09-25
  8. 8
    A Webex Contact Center API connector can be created with Read-Only access, which covers GET calls only, or Read-Write access, which is needed for POST, PUT or update calls.
    Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector · section on connector access rights · Checked 2026-09-25
  9. 9
    With a connector, the connector's Resource Domain holds only the host part of the URL, and the HTTP Request activity holds the request path; putting the path in the connector domain, or the domain in the path, is a configuration mistake.
    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Configure section, method using a connector · Checked 2026-09-25
  10. 10
    The widely repeated 'turn on descriptive logs, open the debug pane, decrypt logs, click the transaction ID' procedure is documented for Webex Connect flows; this packet found no current Cisco document confirming that the same steps apply to Webex Contact Center Flow Designer voice flows.inferred
    Flow Debug · whole page scope (Webex Connect documentation site) · Checked 2026-09-25
  11. 11
    Since the 24 April 2026 Flow Designer update, connecting an End activity to a port is a recommendation rather than a mandatory validation rule, which removes a class of validation errors that previously blocked publishing.
    What's new for administrators in Webex Contact Center · entry dated April 24, 2026 (Flow Designer omnichannel enhancements) · Checked 2026-09-25
  12. 12
    Cisco announced Enhanced Flow Debugging for Flow Designer in December 2025, describing log decryption and search with granular controls and filters while keeping sensitive data protected.
    Flow Designer Enhancements: Transform Customer Interactions with Powerful New Features · Enhanced Flow Debugging paragraph · Checked 2026-09-25
  13. 13
    Cisco publishes an Error Handling Subflow for Webex Contact Center that is meant to handle error conditions in contact handling, such as queue handling problems or failed API requests.
    Error Handling Subflow · page summary paragraph · Checked 2026-09-25
  14. 14
    Flow Designer event flows are optional and asynchronous to the main flow: they can fire at unpredictable points such as agent acceptance, and each event flow needs its own start and end with no activities shared with other flows.
    Build and manage flows with Flow Designer · section 'Canvas, main flow, and event flows' · Checked 2026-09-25
  15. 15
    When diagnosing a queue failure you must read FailureCode against the table for the specific activity that set it, because Queue Contact and Advanced Queue Information use separate numbering.inferred
    Build and manage flows with Flow Designer · sections 'Queue Contact' and 'Advanced Queue Information' failure code tables · Checked 2026-09-25
  16. 16
    FailureCode and FailureDescription output variables are documented on Advanced Queue Information, Escalate Call Distribution Group, Get Queue Info, Queue Contact, Set Contact Priority and Queue To Agent.
    Build and manage flows with Flow Designer · output-variable tables of the named activities · Checked 2026-09-25
  17. 17
    API calls made from Flow Designer are rate limited, and Cisco advises flows to handle HTTP 429 responses gracefully.
    Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector · error-handling guidance section · Checked 2026-09-25
  18. 18
    Since June 2026 Flow Designer provides a 'flow:error' webhook that sends observability events when a flow hits an error, so teams can monitor failed flow executions in near real time.
    What's new for administrators in Webex Contact Center · entry dated June 25, 2026 'Flow Designer error webhook for observability' · Checked 2026-09-25
  19. 19
    Cisco names Splunk as an example of an external analytics platform that can take flow:error webhook events.
    What's new for administrators in Webex Contact Center · entry dated June 25, 2026 · Checked 2026-09-25
  20. 20
    From July 2026 administrators and developers can use the public Flow schema and the Flow V2 APIs on the Webex Contact Center developer portal to author, validate, publish, export and lock flows programmatically.
    What's new for administrators in Webex Contact Center · entry dated July 29, 2026 'Programmatic Flow Design with public Flow Schema and new APIs' · Checked 2026-09-25
  21. 21
    The HTTP Request activity has a 'Use Authenticated Endpoint' toggle: when it is on, the flow uses a connector configured in Control Hub and supplies only the request path, and the connector handles the base URL and OAuth tokens.
    Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector · sections on 'Use Authenticated Endpoint' and request configuration · Checked 2026-09-25
  22. 22
    To call an endpoint with Basic authentication without a connector, turn off 'Use Authenticated Endpoint', enter the full URL, and add an Authorization header whose value is 'Basic' followed by the Base64 encoding of username:password.
    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Configure section, method without a connector · Checked 2026-09-25
  23. 23
    Because Cisco tells developers to check the status code in a Case activity, a non-2xx HTTP response probably continues down the activity's normal output rather than the error path, so a flow with no status check can silently carry on with bad data.inferred
    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · section 'Verify' · Checked 2026-09-25
  24. 24
    The Flow Designer start activity previously called NewPhoneContact is being renamed NewContact as the start node becomes omnichannel; Cisco says work items and digital channels will be added to it later.
    What's new for administrators in Webex Contact Center · entry dated April 24, 2026 · Checked 2026-09-25
  25. 25
    The Flow Designer help article says there is currently no version control feature and that the flow version number just counts how many times the flow has been published.
    Build and manage flows with Flow Designer · section 'Apply version labels to a flow' · Checked 2026-09-25
  26. 26
    OnGlobalError is a Flow Designer event flow for global error handling; it runs when an activity has an error but its error path is not wired, so the flow falls through to the handler configured on the Event Flows tab.
    Build and manage flows with Flow Designer · section 'Event flows' > 'OnGlobalError Workflow' · Checked 2026-09-25
  27. 27
    A Flow Designer flow cannot be published until validation is turned on and every validation error is resolved; the Publish button stays disabled otherwise.
    Build and manage flows with Flow Designer · section 'Footer pane' · Checked 2026-09-25
  28. 28
    The published Queue Contact failure-code table appears to skip code 5 (it goes from 4 to 6), so a FailureCode of 5 cannot be interpreted from the current documentation.inferred
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  29. 29
    Queue Contact failure code 4, INVALID_QUEUE, means the activity specified an invalid queue; code 2, INVALID_ROUTING_STRATEGY, means the chosen routing strategy is invalid.
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  30. 30
    The Queue Contact activity exposes output variables QueueId (the queue the contact was placed in), FailureCode and FailureDescription (set when queuing fails).
    Build and manage flows with Flow Designer · section 'Queue Contact' > output variables · Checked 2026-09-25
  31. 31
    Queue Contact failure codes 9, 10 and 11 (INVALID_SKILL_NAME, INVALID_SKILL_CONDITION, INVALID_SKILL_VALUE) flag an invalid skill name, condition or value in a skills-based queuing request.
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  32. 32
    Queue Contact failure code 12, INVALID_OPERATION_FOR_INTERACTION_STATE, means the contact is in a state that does not allow queuing, such as a terminated contact; code 8, OWNER_ASSIGNED_TO_INTERACTION, means the contact is already assigned to an agent.
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  33. 33
    Queue Contact failure code 6, SYSTEM_ERROR, means the platform hit an internal error; code 1, INVALID_REQUEST, means the parameters in the activity are invalid; code 3, INVALID_WAIT_TIME, means the defined wait time is invalid.
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  34. 34
    Queue Contact failure code 7, VTEAM_TRANSITION_LIMIT_REACHED, means the contact has hit the maximum number of times it can be queued to different queues.
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table · Checked 2026-09-25
  35. 35
    A contact can carry at most 10 skill requirements, and a queue can hold at most 20 Call Distribution Groups and 250 teams across all its Call Distribution Groups.
    System limits in Webex Contact Center · queue and routing limits rows · Checked 2026-09-25
  36. 36
    The Queue To Agent activity reports failure values including AGENT_UNAVAILABLE, AGENT_NOT_FOUND, AGENT_NOT_LOGGED_IN, AGENT_BUSY, FEATURE_NOT_ENABLED, INVALID_VTEAM_ERROR, VTEAM_TRANSITION_LIMIT_REACHED and INVALID_OPERATION_FOR_INTERACTION_STATE.
    Build and manage flows with Flow Designer · section 'Queue To Agent' > failure code table · Checked 2026-09-25
  37. 37
    An HTTP Request that sends a POST or PUT to Webex Contact Center APIs through a Read-Only connector is likely to fail authorisation, so connector access rights should be checked when write calls fail but reads succeed.inferred
    Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector · section on connector access rights · Checked 2026-09-25
  38. 38
    Advanced Queue Information has the highest documented self-loop limit, 1500; Escalate Call Distribution Group has 750.
    System limits in Webex Contact Center · section on self-loop limits for Flow Designer activities · Checked 2026-09-25
  39. 39
    The self-loop limit for the Disconnect Contact activity is 0.
    System limits in Webex Contact Center · section on self-loop limits for Flow Designer activities, row 'Disconnect Contact' · Checked 2026-09-25
  40. 40
    The self-loop limit is 100 for Menu, CollectDigit, Set Caller ID and Set Contact Priority; 50 for Virtual Agent and Virtual Agent V2; 20 for Start Media Stream; and 3 for Upload Audio.
    System limits in Webex Contact Center · section on self-loop limits for Flow Designer activities · Checked 2026-09-25
  41. 41
    Webex Contact Center enforces a self-loop limit of 100 on the Queue Contact activity and 100 on Queue To Agent.
    System limits in Webex Contact Center · section on self-loop limits for Flow Designer activities · Checked 2026-09-25
  42. 42
    The self-loop limit is 10 for Callback, Blind Transfer, Schedule Callback, Record, Recording Control, Call Progress Analysis and FeedbackV2, and 75 for Bridged Transfer.
    System limits in Webex Contact Center · section on self-loop limits for Flow Designer activities · Checked 2026-09-25
  43. 43
    The contact session ID for a Webex Contact Center call can be found in the Real-Time report drill-down, the historical CSR report filtered by ANI or DNIS, the Agent Desktop URL during an active call, or the agent problem report by searching for 'Interaction ID:'.
    Find Contact Session ID for Calls in Webex Contact Center · sections for methods 1 to 4 · Checked 2026-09-25
  44. 44
    In Queue Contact, a weight can only be set on a Proficiency-type skill requirement (otherwise failure code 13, WEIGHT_NOT_SUPPORTED_FOR_SKILL_TYPE), and weights must be integers from 1 to 1000 (otherwise code 14, INVALID_SKILL_WEIGHT).
    Build and manage flows with Flow Designer · section 'Queue Contact' > failure code table rows 13 and 14 · Checked 2026-09-25
  45. 45
    Cisco TAC recommends testing the target API outside the flow first, for example in Postman, and confirming a 200 OK before configuring the HTTP Request activity.
    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Configure section, step 1 · Checked 2026-09-25
  46. 46
    The Flow Designer article documents an Undefined Error path on at least these activities: Advanced Queue Information, Disconnect Contact, Escalate Call Distribution Group, Queue Contact, Screen Pop and Virtual Agent.
    Build and manage flows with Flow Designer · per-activity sections in 'Activities in Call Handling' and 'Activities in Flow Control' · Checked 2026-09-25
  47. 47
    Many Flow Designer activities offer an 'Undefined Error' output path that a flow developer can wire up to handle system errors during flow execution.
    Build and manage flows with Flow Designer · section 'Understand activities and events'; Queue Contact activity description · Checked 2026-09-25
  48. 48
    In Webex Contact Center Flow Designer the flow validation toggle sits on the right of the footer pane and is off by default; turning it on starts backend validation and makes errors in the flow visible.
    Build and manage flows with Flow Designer · section 'Footer pane' · Checked 2026-09-25
  49. 49
    Flow Designer supports Dev, Test and Live version labels for development, staging and production, and the label a contact runs is chosen at the Entry Point.
    Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer · section on Flow Versioning / 'Applying a Version Label to a Flow' · Checked 2026-09-25
  50. 50
    Cisco sources describe flow versioning inconsistently: the help article says there is no version control feature, while a Cisco developer blog describes Flow Versioning with Dev, Test and Live labels, and the July 2026 release note says the Flow V2 APIs keep versioning.disputed
    Build and manage flows with Flow Designer · section 'Apply version labels to a flow' versus webex-dev-blog-flow-designer-adapt-workflows versioning section · Checked 2026-09-25

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

tier 2 current vendor documentation

Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center

Cisco · 2022-03-11 · accessed 2026-09-22

tier 2 current vendor documentation

Error Handling Subflow

Cisco Systems (Webex Help Center) · 2024-09-25 · accessed 2026-09-25

tier 2 current vendor documentation

Find Contact Session ID for Calls in Webex Contact Center

Cisco Systems · 2024-12-09 · accessed 2026-09-25

tier 2 current vendor documentation

Flow Debug

Cisco Systems (Webex Connect documentation) · accessed 2026-09-25

tier 2 current vendor documentation

System limits in Webex Contact Center

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

tier 2 current vendor documentation

What's new for administrators in Webex Contact Center

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

tier 3 vendor-maintained repositories

Flow Designer Enhancements: Transform Customer Interactions with Powerful New Features

Cisco Systems (Webex Blog) · 2025-12-04 · accessed 2026-09-22

tier 3 vendor-maintained repositories

Lab 2(c): Flow Debugging Flows

Webex Contact Center Tech Summit lab repository (Cisco-authored) · 2021-11-09 · accessed 2026-09-25

tier 4 archived vendor documentation

Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector

Cisco Systems, Inc. (Webex for Developers) · 2024-05-13 · accessed 2026-09-04

tier 4 archived vendor documentation

Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer

Cisco Systems, Inc. (Webex for Developers) · 2024-08-07 · accessed 2026-09-04

Cite this page

APA

WarmTransfer. (2026, September 25). Troubleshooting Webex Contact Center flows. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-flow-troubleshooting

BibTeX

@misc{warmtransfer-wxcc-flow-troubleshooting,
  title  = {Troubleshooting Webex Contact Center flows},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-flow-troubleshooting},
  note   = {Verified 2026-09-25}
}