Using Reactive Debugging - Contact Center Express - Cisco DevNet

Publisher

Cisco Systems (DevNet)

URL

https://developer.cisco.com/docs/contact-center-express/using-reactive-debugging/

Published

unknown

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Reactive debugging is started in the Cisco Unified CCX Editor from Debug > Reactive Script, followed by placing the triggering call and stepping with Debug > Continue or Debug > Step Over. in context
• The script name entered for reactive debugging must exactly match the script expression configured on the application, for example SCRIPT[filename.aef] for user scripts or SSCRIPT[filename.aef] for system scripts. in context
• Reactive debugging requires the Unified CCX Engine to be running and the Editor workstation to be connected to the Unified CCX server, and an edited script must be refreshed through Administration before debugging. in context
• Cisco documents reactive debugging as the only way to debug VRU scripts in the Unified CCX Editor. in context
• The reactive debugging Wait Time (Secs) field sets how long the Unified CCX Engine waits for the triggering event or VRU Script request. in context

Cite this source record

APA

WarmTransfer. (2026, October 2). Using Reactive Debugging - Contact Center Express - Cisco DevNet. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-devnet-uccx-using-reactive-debugging

BibTeX

@misc{warmtransfer-cisco-devnet-uccx-using-reactive-debugging,
  title  = {Using Reactive Debugging - Contact Center Express - Cisco DevNet},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-devnet-uccx-using-reactive-debugging},
  note   = {Cisco Systems (DevNet), accessed 2026-10-02}
}