Closed cjames1224 closed 6 years ago
Hi Christian, According to my tests the serverTimestamp is not present on any ms.MessagingEventNotifications of type ChatStateEvent, but is present consistently for other event types. Are these your findings as well? If not please give some more details about the types of events that are lacking this property.
I see that the documentation does list this as a required parameter of the response, so I am reaching out to the owner of this system to determine the expected behavior and update the documentation accordingly.
Thank you, Mark. Yes you are correct, we are not seeing the serverTimestamp on ChatStateEvent responses. And also, as you've stated, the expectation was that it is a required parameter of the response.
On Fri, Oct 27, 2017 at 5:34 PM, Mark notifications@github.com wrote:
Hi Christian, According to my tests the serverTimestamp is not present on any ms.MessagingEventNotifications of type ChatStateEvent. Are these your findings as well? If not please give some more details about the types of events that are lacking this property.
I see that the documentation does list this as a required parameter of the response, so I am reaching out to the owner of this system to determine the expected behavior and update the documentation accordingly.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LivePersonInc/node-agent-sdk/issues/35#issuecomment-340094704, or mute the thread https://github.com/notifications/unsubscribe-auth/AAt0qHmqwo1YnrhpQPtvlkuX53i_F6iLks5swkxqgaJpZM4QJOcB .
Hi Christian,
I have received confirmation that the ChatStateEvent lacks a timestamp by design, and it is the only such event. I will work to ensure that the documentation is updated accordingly.
Understood, thanks Mark. Can close this issue when ready.
On Wed, Nov 1, 2017 at 3:29 PM, Mark notifications@github.com wrote:
Hi Christian,
I have received confirmation that the ChatStateEvent lacks a timestamp by design, and it is the only such event. I will work to ensure that the documentation is updated accordingly.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LivePersonInc/node-agent-sdk/issues/35#issuecomment-341213810, or mute the thread https://github.com/notifications/unsubscribe-auth/AAt0qBLMfHFhkw9r5LXiNHEaCCIJygS8ks5syMakgaJpZM4QJOcB .
The serverTimestamp property is only intermittently available in ms.MessagingEventNotification response. For code that requires the serverTimestamp, this is problematic. Is this expected behavior?