conversations always falls back to root level. child nodes not reached

  • Resolved guenstig

    (@guenstig)


    6 years, 1 month ago

    I have problems with my chatbot. I am trying to set up a conversation where the user can select multiple options and dependent on the selection the conversation continues. However, it seems that the conversations start from the root level after each answer and never enters any child nodes. If I have the nodes which react to the entities on the root level it works, however, I want to avoid that the user can directly enter these nodes. Also, I noticed that when looking at the conversation logs there are no ongoing conversations, each answer is treated as a new one.

    I’ve been reaching for an answer to this for quite some time and what I noticed that this problem is similar to when someones using a programmatical approach to watson, like using node.js, and then forgets to return the conversation-context (and/or conversationID)
    However, since I am using the watson plugin this should be handled. Is there anything that might go wrong in the configuration? When I am testing my bot on the Watson Assistant workspace GUI then there is no problem. Only then on the WordPress website, the bot seems to forget that the conversation has already started.

    Might this be caused by the free plan I have? Are there only root level conversations possible?

    • This topic was modified 6 years, 1 month ago by guenstig.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Ambyomoron

    (@josiah-s-carberry)

    I have never seen this myself. I would ask if you have set up any context variables in the plugin, that being the essential functional difference between the front end and the back end.

    Thread Starter guenstig

    (@guenstig)

    No, I haven’t set up any context variables in the plugin. What I have noticed is that the problem appears when I use options. If I select an option then the bot does not recognize the answer, if I type the value of the option it works. In the “try it” bot on IBM Assistant, it works both ways.

    • This reply was modified 6 years, 1 month ago by guenstig.
    • This reply was modified 6 years, 1 month ago by guenstig.

    i have the same problem with options.

    Plugin Author intelahelp

    (@intelahelp)

    Hello!

    Please clarify if the issue is still present.

    luisjimeno2019

    (@luisjimeno2019)

    Dear partners

    I have the same issue with options. When I configued the options, they works perfect on try it o the IBM workspace but on the web page it oes until anything_else trigger

    Could you please advice?

    Regards

    Luis

    Plugin Author intelahelp

    (@intelahelp)

    Hello Luis.
    Could you, please, provide a JSON snapshot of the relevant workspace? You can get one with “Download as JSON” context menu at your Watson Assistant Workspaces dashboard.

    Plugin Author intelahelp

    (@intelahelp)

    Please update the Watson Assistant plugin to the 0.7.8. This version addresses the issue with dialog options button functionality.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘conversations always falls back to root level. child nodes not reached’ is closed to new replies.

Tags