Trouble With Play Module

[KReidy]

Sorry but this is my third attempt trying to get this topic posted

 

I am having some trouble with a Play module, the module plays the message file and then hangs, it does not go to the next module after the message has played but hangs up eventually.

 

I have attached a log file.

 

From the log file you will see that I can use play modules in the script see lines

 

1234358.906 12 73

 

The bad module is located on line 1322251.343 13 88

 

on line

132256.781 6 88 I get the following error message

 

Error V7.0.3149.39709 LsPlayMsg:Input string was not in a correct format

 

I hope youcan help me

1008_1242_vgEngine.txt

[SupportTeam]

Could you please post the "Paths" definitions from module [FirstYearGroup/IndividualMessageCPC1]

 

As an immediate workaround for this bug please see if doing this works around the problem:

Remove the word/substring "timeout" from any of the module names in your script. This would result in removal the word "timeout" from any of the paths unless an actual Timeout type path was specified.

 

Seeing the "Paths" definitions from module [FirstYearGroup/IndividualMessageCPC1] will let us confirm if the above was in fact what was casing the problem. We are also currently looking at this section of VoiceGuide code and next release of VoiceGuide v7 will not have this bug anymore.

 

[KReidy]

I started to do as you suggested, I looked at my code using a vbscript editor.

 

I found the following for the path definition

 

on {timeout} goto [Replay FirstYearGroup/IndividualMessageCPC]

 

I changed the path to the following

on {timeout 0} goto [Replay FirstYearGroup/IndividualMessageCPC]

 

 

Hey presto it is now working!!! I don't know why the timeout had no value assigned to it in the first instance, when you select it in the script editor it defaults to {timeout 0}?

 

Thanks for your help

[SupportTeam]

Thanks for letting us know what the problem was.

 

The script designer should assign a default value of 0 to a Timeout path, so it is unexpected to see no value there. We'll have a look at that part of the code again to ensure this case is handled better if other scripts omit the timeout value.