Reporting event caused by manual API call caused routing queue volume

This issue occurs when the Chat server End Conversation API is called without a timestamp.

Scenario

This API is called by the Bot and it may only happen if the Bot is not trained to call the API with the required set of attributes.

Impact

All reporting-queue events are piled up in the reporting queue.

Workaround

For a quick fix of this issue, a manual operational activity is required.

Resolution

A permanent fix is done in 3.16.0. The API doesn't accept requests if there are missing required parameters.