I have created few dialogs in the watson console and in try it out panel the nodes are traversed by in proper way by giving priority to child nodes but in android app (watson android sample) it gives priority to the outer nodes.
Why there is a different behaviour in try it out panel and android application?
My guess is that you are not reusing the session context and starting a new session for each call into Conversation. You need to send the session context that is returned from Conversation together with the new input back to Conversation. Thus, the dialog can be picked up at the node where it left. The API calls are stateless and you need to provide it as part of the call.