After update to v0.8.16 chat doesn’t start anymore

  • Resolved nicoter

    (@nicoter)


    5 years, 5 months ago

    Hi,

    After updating to the latest version the chat doesn’t initiate the conversation flow anymore. But when clicking the trash icon it will start with the flow.

    I have disabled cache and tried in different browsers.
    I’m sending you the full log.

    Thanks

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter nicoter

    (@nicoter)

    FYI: I rolled back to version 0.8.15 and it works again.

    Plugin Author Intela-bot Help

    (@intelahelp)

    Hello @nicoter.
    We released the new version of plugin (0.8.18) that has the fix to your issue. Please update your plugin to the latest version and let us know if the issue persists.

    I am still having the above issue with 0.8.18. The welcome message will initiate (even when changed in Watson Assistant in IBM Cloud) but messages can not be sent.

    Here’s some log messages:

    from console: 

    
Error: "Message could not be sent."
    value https://chatmetwillem.nl/wp-content/plugins/conversation-watson/app.js?ver=0.8.18:1

    from WP:

    Event 5d9c3431f1770, 2019-10-08 07:01:05

#8: Watson Assistant response error

Service Unavailable - Zero size object

The server is temporarily unable to service your request.  Please try again
later.

Reference #15.d7f31502.1570518065.1030597

    No messages are sent to IBM, as the analytics tab doesn’t list them.

    Thread Starter nicoter

    (@nicoter)

    FYI: I can’t comment if 0.8.18 fixed the bug, because I’m still on 0.8.15.

    Plugin Author Intela-bot Help

    (@intelahelp)

    A lot of IBM Watson Assistant Plugin customers reported on the forum as well as by email about the “500 Internal Server Error”.

    This error is caused by recent change to Watson Assistant v2 API. This change is not described in the official documentation:
    1. https://cloud.ibm.com/apidocs/assistant-v2#create-a-session, screenshot;
    2. https://cloud.ibm.com/docs/services/assistant?topic=assistant-api-client-get-context, screenshot.

    Before the API was changed, “context” object structure (in the response from Watson Assistant) was:
    {"context": {"skills": {"main skill": {"user_defined": {}}}}}.

    Then there was added a new undocumented “system” object and now “context” object structure is:
    {"context": {"skills": {"main skill": {"user_defined": {}, "system": {}}}}},
    screenshot.

    Due to the difference between documented structure and the actual one Plugin fails with “500 Internal Server Error”.

    We are working on fixing it.

    Plugin Author Intela-bot Help

    (@intelahelp)

    Hello @remyreurling.
    We released the new version of plugin (0.8.19) that has the fix to your issue. Please update your plugin to the latest version and let us know if the issue persists.

    Thread Starter nicoter

    (@nicoter)

    Version 0.8.19 is working for me and also fixed the initial bug introduced with 0.8.16.

    Thanks @intelahelp!

    Plugin Author Intela-bot Help

    (@intelahelp)

    You are welcome!

    Plugin Author Intela-bot Help

    (@intelahelp)

    Hello @remyreurling.

    We haven’t heard from you recently.
    Do you still have any questions or need our assistance?
    We will gladly help you.

    Hi @intelahelp,

    I replied to your email instead.

    As with OP, the issue was fixed with the introduction of 0.8.19. Thanks for the response.

    Plugin Author Intela-bot Help

    (@intelahelp)

    @remyreurling.
    We are glad that everything works for you now.
    Thank you for letting us know.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘After update to v0.8.16 chat doesn’t start anymore’ is closed to new replies.