Genesys Cloud - Main

Hello all!

I am a bot architect and am running into some issues with the Loop Until function. Previously, I was able to, when the user came into a particular task, check the last complete utterance using the session.lastcompleteutterance variable for a slot. If the slot was missing, I would loop the user back through an ask for slot action and the loop would reevaluate using the selected slot. Once the slot was present, pass the user to a switch that would check for an additional slot. 

For some reason, now the Loop Until will bypass the function all together. I haven't changed anything, and I don't see any updates that would have affected this. 

When I remove the Loop Until Action, the Switch properly evaluates the utterance for the necessary slot, but this requires the use of an Ask for Slot function to ensure the user gets to the correct path. I am trying to avoid asking for a slot if a member has already provided the information as was the case about a month ago. Can anyone shed some light on this?

Hello all!

I am a bot architect and am running into some issues with the Loop Until function. Previously, I was able to, when the user came into a particular task, check the last complete utterance using the session.lastcompleteutterance variable for a slot. If the slot was missing, I would loop the user back through an ask for slot action and the loop would reevaluate using the selected slot. Once the slot was present, pass the user to a switch that would check for an additional slot. 

For some reason, now the Loop Until will bypass the function all together. I haven't changed anything, and I don't see any updates that would have affected this. 

When I remove the Loop Until Action, the Switch properly evaluates the utterance for the necessary slot, but this requires the use of an Ask for Slot function to ensure the user gets to the correct path. I am trying to avoid asking for a slot if a member has already provided the information as was the case about a month ago. Can anyone shed some light on this?

Ask for slot action will never ask for the slot if it is already filled.  - This is a feature. Think of an Intent with a phrase that has a slot. Customer says I want to buy a red bike, and red and bike are slots. In the Purchase intent, I already know they product and type, so the Ask for Slot in that intent will skip, if the customer only said I want to buy a bike the same ask for slot in the same place then would ask for that slot.

So as Robert suggested, if you use the clear slot action that clears it so when it gets to the Ask for Slot action it will then ask for it again.

Hello all!

I am a bot architect and am running into some issues with the Loop Until function. Previously, I was able to, when the user came into a particular task, check the last complete utterance using the session.lastcompleteutterance variable for a slot. If the slot was missing, I would loop the user back through an ask for slot action and the loop would reevaluate using the selected slot. Once the slot was present, pass the user to a switch that would check for an additional slot. 

For some reason, now the Loop Until will bypass the function all together. I haven't changed anything, and I don't see any updates that would have affected this. 

When I remove the Loop Until Action, the Switch properly evaluates the utterance for the necessary slot, but this requires the use of an Ask for Slot function to ensure the user gets to the correct path. I am trying to avoid asking for a slot if a member has already provided the information as was the case about a month ago. Can anyone shed some light on this?

Ask for slot action will never ask for the slot if it is already filled.  - This is a feature. Think of an Intent with a phrase that has a slot. Customer says I want to buy a red bike, and red and bike are slots. In the Purchase intent, I already know they product and type, so the Ask for Slot in that intent will skip, if the customer only said I want to buy a bike the same ask for slot in the same place then would ask for that slot.

So as Robert suggested, if you use the clear slot action that clears it so when it gets to the Ask for Slot action it will then ask for it again.

Hello all!

I am a bot architect and am running into some issues with the Loop Until function. Previously, I was able to, when the user came into a particular task, check the last complete utterance using the session.lastcompleteutterance variable for a slot. If the slot was missing, I would loop the user back through an ask for slot action and the loop would reevaluate using the selected slot. Once the slot was present, pass the user to a switch that would check for an additional slot. 

For some reason, now the Loop Until will bypass the function all together. I haven't changed anything, and I don't see any updates that would have affected this. 

When I remove the Loop Until Action, the Switch properly evaluates the utterance for the necessary slot, but this requires the use of an Ask for Slot function to ensure the user gets to the correct path. I am trying to avoid asking for a slot if a member has already provided the information as was the case about a month ago. Can anyone shed some light on this?

Just a guess here, but I would guess that the Maximum defaults to 0 or 1 and that allows no looping at all.  

Ask for slot action will never ask for the slot if it is already filled.  - This is a feature. Think of an Intent with a phrase that has a slot. Customer says I want to buy a red bike, and red and bike are slots. In the Purchase intent, I already know they product and type, so the Ask for Slot in that intent will skip, if the customer only said I want to buy a bike the same ask for slot in the same place then would ask for that slot.

So as Robert suggested, if you use the clear slot action that clears it so when it gets to the Ask for Slot action it will then ask for it again.

Hello all!

I am a bot architect and am running into some issues with the Loop Until function. Previously, I was able to, when the user came into a particular task, check the last complete utterance using the session.lastcompleteutterance variable for a slot. If the slot was missing, I would loop the user back through an ask for slot action and the loop would reevaluate using the selected slot. Once the slot was present, pass the user to a switch that would check for an additional slot. 

For some reason, now the Loop Until will bypass the function all together. I haven't changed anything, and I don't see any updates that would have affected this. 

When I remove the Loop Until Action, the Switch properly evaluates the utterance for the necessary slot, but this requires the use of an Ask for Slot function to ensure the user gets to the correct path. I am trying to avoid asking for a slot if a member has already provided the information as was the case about a month ago. Can anyone shed some light on this?