Because retries are built by handling the CallbackFailed event, a flow with no CallbackFailed handler probably does not retry a failed callback on a schedule the reader controls.

inferred · Checked 2026-09-30

Vendor
Cisco
Product
Webex Contact Center
Subsystem
Flow Designer event flows
Deployment
multi-tenant
Region
not restricted
Release range
current as of 2026-09-30
Status
inferred
Checked
2026-09-30

Sources

Cite this note

APA

WarmTransfer. (2026, September 30). Setting up callbacks in Webex Contact Center: source note wxcc-callback-setup-no-handler-no-retry. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-callback-setup-no-handler-no-retry

BibTeX

@misc{warmtransfer-claim-wxcc-callback-setup-no-handler-no-retry,
  title  = {Setting up callbacks in Webex Contact Center: source note wxcc-callback-setup-no-handler-no-retry},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/wxcc-callback-setup-no-handler-no-retry},
  note   = {Source note wxcc-callback-setup-no-handler-no-retry, checked 2026-09-30}
}

Read in context