Upload configuration is creates different dialog than uploading it through the browser.
This problem has been occurring since last week, around june 7th 2017.
I'm running some python code which generates a configuration.json file to upload to watson through the API. This used to work fine until june 7th where suddenly all "go_to" jumps are ignored. (Moving to the body of another dialog_node).
What makes this even more interesting is that if I upload that same configuration through the browser as a new workspace, then the "go_to" jumps are NOT ignored and it works just fine.
Some example json for a go_to dialog_node:
{ "description": null,"conditions": "anything_else","go_to": { "return": null,"dialog_node": "say_hello","selector": "body"},"output": { "text": { "values": [],"selection_policy": "sequential"} },"dialog_node": "go_to_say_hello,"created": "2017-06-12T10:01:50.064Z","updated": "2017-06-12T10:01:50.065Z","metadata": null,"parent": null,"previous_sibling": null,"context": {}},
The question is: Have others encountered this as well? Was there a fix?
If you using the same configuration file, generated by your Python app to upload via the browser, then the difference will be how your Python apps handles the goto references.
Are you running the Python app on your machine or in Bluemix? Did you update the version of Python you are running on. Did you pip install a new version of watson-developer-cloud?
This has to do with the api version of us updating the json schema. See the release notes here: https://console.bluemix.net/docs/services/conversation/release-notes.html#release-notes I think the change was actually May 26, so check that date first.