Skip to main content
1. New

Resolver strategy options are not aligning correctly with the slot values.

Related products:AI Assistant
  • September 29, 2025
  • 5 replies
  • 35 views

Resolver strategy options are not aligning correctly with the slot values. Based on our analysis, the resolver strategy options are not appearing in the defined order and are getting mixed up with slot collection values. Sometimes the resolver strategy options appear first, while other times they appear last, which may create confusion for the user.

We are observing this issue more frequently in flows that do not require a decision policy. However, even in flows built with a decision policy, the resolver strategy options are not behaving consistently.

We request the product team to look into this and provide a controlled option flow for the user to ensure a better experience.

5 replies

Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • September 29, 2025

@Samaran - Are you asking for a way to select the order in which the slots get prompted to the user?


  • Author
  • New Participant
  • September 30, 2025

@Kevin Mok - Partially correct. When we define steps in the conversational process, we provide step by step details in the content activity and select slots in that same order in action activity. However, the resolver strategy options are appearing either at the top or at the bottom for the user, rather than in the specified order.


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • September 30, 2025

@Samaran Can you provide screenshots? It’s hard to visualize it.

 


  • Author
  • New Participant
  • October 1, 2025

 ​@Kevin Mok 

In one of our use cases, we have 4 steps to complete a request. For one of these steps, we need to define a slot with a resolver strategy (.value). However, out of the 4 sequential steps, the slot with the resolver strategy (.value) is appearing at the top of the chat for the user.

Conversation ID: GD6zefeYWmR2
 


Irrespective of the order resolver strategy(.value) option appearing at the top for the user to complete a request. 

Please note that we shared just one instance in one of our use case. We noticed this that slots that are defined with resolver strategy(.value) are fluctuating. They are not according to the order of the flow. Please check


Forum|alt.badge.img+1
  • Known Participant
  • January 16, 2026

I have noticed this as well. If I am asking for multiple slots at the same time, it will ask for all of them at one, one line at a time; however the order of them can change between plugin calls. If the user is familiar with the plugin they may copy the responses in order, but that may not be correct in the next plugin call iteration. I notice this often when testing plugins I build.