The timeout outcome means no API response was received within the agreed time, so it does not say whether the transfer happened, and a flow taking that branch cannot know the conversation's state.
inferred · Checked 2026-09-15
Could not receive an API response from WxEngage within the agreed time-out
- Vendor
- Cisco
- Product
- Webex Connect
- Subsystem
- Conversation transfer
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-15
- Status
- inferred
- Checked
- 2026-09-15
Sources
- Transfer conversation - WxEngage standalone — Cisco Systems, Inc. (Webex Connect documentation) · tier 2 current vendor documentation · Transfer conversation node, Node outcomes, onTimeout
Cite this note
APA
WarmTransfer. (2026, September 15). Transferring a digital conversation in Webex Contact Center: source note wxdxfer-timeout-is-an-unknown-outcome. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxdxfer-timeout-is-an-unknown-outcome
BibTeX
@misc{warmtransfer-claim-wxdxfer-timeout-is-an-unknown-outcome,
title = {Transferring a digital conversation in Webex Contact Center: source note wxdxfer-timeout-is-an-unknown-outcome},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxdxfer-timeout-is-an-unknown-outcome},
note = {Source note wxdxfer-timeout-is-an-unknown-outcome, checked 2026-09-15}
}