UCCX script not answering the call

[ImTheGame56]

Hi All,

My first post but I'm coming across a strange problem and i guess i just need a second set of eyes to steer me in the proper direction.

Here is the scenario:

I have a working script where i call the trigger and it answers (ie...reactive debug is able to step through) - this is a test Call Control Group so its separate from the production environment. This proves the trigger and script are working correctly enough for the debug to step through

When i change the script and click update - I call the script and I get "i'm sorry we are currently experiencing system problems and are unable to process your call". Its using the same trigger, so I would expect that I would at least be able to step through the script (even if the script is not correct). However, when i call it I get that message and the reactive debug just times out.

Any thoughts?

[seanvaid]

So are you saying this is a new script that was working in a test environment, but failing when implementing in production?

[ImTheGame56]

No, it was failing in a test environment. 

But I believe i found the problem.  I had a subscript (holiday script) in the script that was non-existence in UCCX so thats why it was failing.

[seanvaid]

Makes sense.

The error message you're hearing is due to the main script trying to trigger the subscript.

[ImTheGame56]

Its just weird because the subscript is lower down on the logic of the script and when i called the trigger it wouldn't even hit the reactive debug

[seanvaid]

That is weird. You might have issues with the trigger / ccg / cucm.

Let me know if deleting the subscript does it, I'm very curious. 

[ImTheGame56]

Deleting the subscript did work.

I was able to see the reactive debug fire up and step through the process. 

Such a weird error

[seanvaid]

Interesting. I guess the main script triggers the subscript right away, without ever even reaching the step..

Regardless, glad to hear it's fixed. 

[ImTheGame56]

Thanks for responding!