Skip Navigation
Expand
When using the Chat UQ API, chats are not being delivered and message size quota exceeded error in logs
Answer ID 9249   |   Last Review Date 12/23/2018

While using the Chat UQ API, why are chats not being delivered and error messages in the logs are referring to maximum message size quota for incoming messages being exceeded?

Environment: 

Chat UQ API

Issue:

This happens when specifying a starting sequence number of zero and, eventually, too many messages build up and are returned on the 'retrieveMessages' API call to be processed.  Errors observed in logs indicate message size quote is exceeded.

Resolution:

A null should be sent in the starting sequence number field and let the chat server keep track of which messages have been sent.  The starting sequence number should only be used to attempt to recover from a system problem that caused the Chat UQ API to miss some messages that had been sent.

For example:

<StartingSequenceNumber>0</StartingSequenceNumber>

should be:

<StartingSequenceNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>

Please refer to the "RetrieveMessages" documentation on how StartingSequenceNumber should be used:

http://documentation.custhelp.com/euf/assets/devdocs/unversioned/Chat_APIs/Default.htm

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.