Not sure if this is a bug or an enhancement request, but I tried sending a text variable as input to a conversation task and the variable was not resolved to its text value.
This can be tested by making a dummy conversation topic matching the name of your variable, such as %texttopic%, and entering a message such as "The variable was not replaced."
Make a task which has a conversation action and give it the variable reference as a parameter (which defaults to %text%), and you will see your custom failure message. |
Sending a variable as a parameter for a conversation task should resolve to its text value
