Participant Data Limits

[javier.delolmo]

Hi!
I have a question about participant data, is there a limit on the amount of participant data a conversation can have?

[Eos_Rios]

technically no, but it's a really bad idea to put too much in there because it has a performance impact on the system since it passes the entire conversation around like a hot potato between microsystems and all that bloat goes on every hop.

[Dileepkaranki]

Regarding this we got an issue where we are not able to get all participant data in the API response.
So customer opened a case with Genesys to check the issue.
When we checked with Genesys support team regarding missing participant data below is the response
The API is not returning all the information due to this API limit.
https://developer.genesys.cloud/organization/search/conversation-participant-attribute-search#general-information

• We only store conversations with attributes <20KB
• The max response size for this endpoint is 1 MB

Also, When it got enabled, customer claimed they were storing 36 characters. (0003429740)

So the solution here is to store less information or use the API GET /api/v2/conversations/calls/{conversationId} to get attributes for interaction one by one,
but please be aware that using this method can cause other limits to be reached.

[Adrian_Santamaria]

I think I made some tests in the past and when retrieving the Participant Attributes using one of Analytics API Job or Conversations API (I do not remember which one) each attribute length was capped at 1024 characters while being whole with the other one...