Answered

How to route 'Ask a Question' node to the Else/"All Other Conditions" branch in Copilot Studio

(0) Share

Report

Posted on by SR-24020711-0

Hi Community,

I'm working on a topic in Microsoft Copilot Studio regarding 'feedback' and using an 'Ask a Question' node with a ClosedListEntity (Yes/No options). I have condition branches set up for each expected answer, but I'm trying to understand how the flow can be directed to the 'All Other Conditions' (Else) branch, if end user doesn't give the feedback (Yes/No options).

Specifically, I'd like to know:

- Under what circumstances does the flow fall through to the Else branch when using a ClosedListEntity — for example, if the user types something unexpected or triggers an interruption?
- Is it possible to intentionally route to the Else branch programmatically, such as by setting the variable to an unrecognized value?
- Are there any best practices for handling unexpected or out-of-scope responses within a 'Ask a Question' conditional flow before it escalates to the Fallback topic?

My current setup has allowInterruption: true on the Question node, so I'm also wondering whether an interrupted flow resumes at the Else branch or simply exits the topic entirely.

Any guidance or examples would be really appreciated. Thanks in advance!

Categories:

Topic creation & management

General topics

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Sayali-MSFT Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hello,
In Copilot Studio, a ClosedListEntity (e.g., Yes/No) does normalization, not raw input capture. The system will continuously re-prompt the user until it can confidently map the response to one of the defined values or the topic exits due to interruption or fallback. Because of this behavior, the “All Other Conditions” (Else) branch is almost never triggered directly from user input when using a ClosedListEntity.

Unexpected text, emojis, silence, or off-topic responses do not trigger Else — they trigger re-prompts. The Else branch only runs if the Question node successfully completes and the resulting variable does not match any defined condition. This typically happens only when the variable is set programmatically to an unexpected value, when entity options are modified without updating conditions, or when the variable is overwritten or manipulated in the flow.

Interruption (allowInterruption = true) exits the topic entirely; it does not route execution to Else, nor does the flow automatically resume afterward. If resumable behavior is required, state must be persisted and explicitly re-evaluated.

If your goal is to handle “invalid” or “no answer” scenarios, you should not rely on Else. Instead, use retry limits, explicit skip options, timeout handling, or sentinel values set programmatically. If true Else-style behavior based on user input is required, use a text input with manual normalization instead of a ClosedListEntity.

Key takeaway:
Else is a logical fallthrough, not a validation fallback. ClosedListEntity handles validation through re-prompting, not branching.

Was this reply helpful? Yes No
SR-24020711-0 37 on at

Like
a
(0)

Report
Copy link

Link copied!

@Sayali Thanks for such a prompt and descriptive response. It did clarify my doubt on flow interruption and fallback. That was helpful.

Was this reply helpful? Yes No
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello SR-24020711-0 ,
Glad to hear that your issue is resolved!!
Your feedback is important to us. Please rate us:

🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Was this reply helpful? Yes No