Post live chat message not triggering recieve event

[danieljimeneznz]

Hi, I wasn't sure where to report this bug - but I have noticed an inconsistency in the events mechanism, specifically the recieve event does not fire when a message gets sent by the assistant when the user disconnects from an agent.

To recreate this, simply add a recieve listener to the watson instance with a service desk on the project and note the lack of this event firing after the user disconnects and the default message gets sent. I expect this event to be triggered, and don't believe this message is triggering any events listed in the api events documentation.

[TazmanianDI]

You are correct that this is the current behavior. The receive event is only fired for messages that are actually sent by the assistant service and received by web chat. Messages generated internally by web chat (there's not many but the message you mention is not the only one) do not trigger the receive event.

And so, you are unfortunately correct in that there's currently no event you can use to capture this message. Do you have a specific reason to do so?

[danieljimeneznz]

You are correct that this is the current behavior. The receive event is only fired for messages that are actually sent by the assistant service and received by web chat. Messages generated internally by web chat (there's not many but the message you mention is not the only one) do not trigger the receive event.

And so, you are unfortunately correct in that there's currently no event you can use to capture this message. Do you have a specific reason to do so?

That's a real interesting one, would that mean there is no way to customize this response? My specific reasoning was to make sure that every message via the recieve event gets sent somewhere for logging and auditing purposes - i.e. to always know exactly what has been sent to the user. I've semi ditched my intended plans for sending this message so don't necessarily need to do this anymore but just found that it's interesting behavior...