This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Calling beginDialog from inside a ask() handler causes a message to be skipped
#1932
Comments
benbrown
changed the title
ask() handler causes a message to be skippedask() handler causes a message to be skipped
benbrown
added a commit
that referenced
this issue
Mar 13, 2020
…the handlers to fire without interferring with the following message in the dialog
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due to the way the dialog stack works, calling a
bot.beginDialog()inside anask()handler will cause the next step of the dialog in which theask()is called to be skipped.This is because the
ask()handler actually fires during the first phase of processing that next step, and when the beginDialog occurs, the process is short circuited. There is currently no way to resume at that step after the child dialog has completed.One possible solution is to split the message into 2 actual steps, one solely for processing the response to the question and a second to send the following message. This can theoretically be achieved inside the .ask function.
The text was updated successfully, but these errors were encountered: