Ccrooked-brown
Bug when using Choice Step reprompts
Observed Behavior: The No Reply reprompt feature in the Choice Step is behaving randomly. When configured with two distinct, hard-coded text messages in the "Reprompt 1" and "Reprompt 2" slots, the agent's output is not sequential. Sometimes it sends the first message twice, other times the second message twice, and other times it works correctly (message 1, then message 2). The behavior is inconsistent across multiple test runs.
Expected Behavior: According to the documentation, the reprompt slots should act as a sequential queue. The 1st timeout should always trigger Reprompt #1. A 2nd consecutive timeout should always trigger Reprompt #2. The behavior should be deterministic.
Steps to Reproduce:
1. Create a Choice Step in a workflow.
2. Enable the No Reply path with 2 reprompts.
3. In the "Reprompt 1" text field, type a unique static string (e.g., "This is message 1").
4. In the "Reprompt 2" text field, type a different unique static string (e.g., "This is message 2").
5. Run the prototype test. Wait for the first No Reply timeout and observe the message.
6. Continue to wait for the second No Reply timeout and observe the second message.
7. Repeat the test multiple times to see the inconsistent and random sequencing of the reprompt messages.
Expected Behavior: According to the documentation, the reprompt slots should act as a sequential queue. The 1st timeout should always trigger Reprompt #1. A 2nd consecutive timeout should always trigger Reprompt #2. The behavior should be deterministic.
Steps to Reproduce:
1. Create a Choice Step in a workflow.
2. Enable the No Reply path with 2 reprompts.
3. In the "Reprompt 1" text field, type a unique static string (e.g., "This is message 1").
4. In the "Reprompt 2" text field, type a different unique static string (e.g., "This is message 2").
5. Run the prototype test. Wait for the first No Reply timeout and observe the message.
6. Continue to wait for the second No Reply timeout and observe the second message.
7. Repeat the test multiple times to see the inconsistent and random sequencing of the reprompt messages.
