I've noticed that in the literal config of a loop one is limited to a 99 count.
However, I've noticed that we can write Count() expressions and have used them in loops effectively.
Is there a way that we could write an infinity loop with an expression? I've been looking around the interwebz for something comparable that I could apply in PC. One thought I had is using ++
Would an operator work or is Purecloud limited to a set number of loops (99)?
Maybe something like Task.Loop++ or maybe something Count(Task.loop=1++)
I know the latter is probably not right because its string to integer, but I'm just throwing ideas around.
Use the Update Data action inside the loop to set the index variable to a number less than the loop count. Use with caution. Infinite loops are normally a bad idea; at some point you'll probably want to kick out of the loop and do something else.
Melissa,
Thanks for the reply. Follow up question;
If I do use an infinity loop as you showed in your reply, my only concern is that... could it break architect or cause any adverse effects (i.e. call getting stuck or bringing architect down) ? Or is the caution more that caller gets stuck in the loop with no out option?
You won't break architect or your edge, it's more about your caller having a bad experience from being unable to use your IVR. Eventually the caller will run out of patience and hang up, but they'll be mad at you when they do.
For example, if you are using the collect input action to get information from a caller but they can't enter a valid value after X tries (5, 10, 99, whatever max you think is reasonable), they should be redirected to an agent or some other option.
If you're using a bridge or data action and get a failure or timeout outcome, retrying a few times may make sense (*depending on what the action is doing--fetching an account balance is retryable, making a payment is not) but retrying for 15 minutes while the customer is waiting on the line wouldn't be a good idea--again transfer to an agent or try something else.
Lastly, in general writing an infinite loop while planning to add a logic inside it that will break out of the loop is a bad idea because it's very easy to overlook one of the paths and make it a truly infinite loop with no way out (other than getting mad and hanging up).
