Plum IVR Support

Is there a hard limit on the number of characters that can be returned to a <data> tag?

We have a large dataset being returned and it looks like it breaks at a little over 35,000 characters.

If not, is there a limit on the number of repeated items in a list?
ie:
<data>
<item>
</item>
<item>
</item>
<item>
</item>
<data>

We have around 98 in the test data, but it is failing more in the 75 range.

Hello,

There is no hard coded limit on the <data> tag return value. What IVR errors are your seeing in your IVR last call log when the data tag exceeds 35,000 characters? Also, the limit on the number of items in a single form is currently capped at 100. You can perform a transition to a new form if you reach that limit.

Obviously you are free to code your IVR application however you want, but I would advise against using the IVR tag, data, for this purpose, it is far less efficient than using standard page transition to provide information to users. It's primary intent was for small data exchanges for semi-realtime interaction. Anything larger than that should simply perform the page transition and generate a new VoiceXML document with the information needed to be played to the user.

Regards,
Plum Support

Actually, I was not asking about the number of Items in a form, but the number of repeated data items in an xml tag returned to a callout to a url by the <data> tag. (see my previous post)

What I am doing, is looping through 5 items at a time and playing them to the user. I was trying to avoid the time delay for a page fetch between each group, and the added database overhead of the same. I was getting about 100 items back, but the script appears to fail with anything over about 75 items. At that number the xml blob is about 35K bytes.

Is this the number of xml Items, or the size of the xml blob returned?

Hello,

Could you please provide more information about exactly what is happening? Please include sample vxml code and the appropriate IVR last call log data. Without that information your descriptions are too high level to give us anywhere to start debugging the IVR problem.

Again we would like to stress that this is not a correct use of the IVR tag, <data>, and you would be far better served by using the IVR tag, <submit>, or even the IVR tag, <subdialog>.

Regards,
Plum Support