WebHook payload limit clarification

[LifeOmic-Dev]

I just had some questions concerning your WebHook post notifications and the frequency/payload sizes. I am getting very large payloads of updates sometimes and we have been doing lots of research in your docs and this forum for information. On the forum, it does list this as in issue explained here, and it states that there is no limit on the size of the payload that can be posted. A different source from your documentation lists that the maximum number of notification joined together is 100. I guess my question is can you explain what that means, and if the size of payloads is still unbounded, does your side have the capabilities to split up notification payloads so that we can pull in data in smaller chunks? 

[Gordon-C]

Hi @LifeOmic-Dev 

I believe our systems have changed over the years since the statement you found says "no limit".   I can tell you the information in the documentation of 100 notifications joined together is incorrect.   Today, our system is configured to batch messages that pile up in 0.5 seconds up to 2000 records.  

[LifeOmic-Dev]

Thanks for the reply! Are you able to reduce that batch/record size per subscription endpoint? Something like 1000 records? Also, what happens to the notifications that fail due to the limit? I wasn't sure if you re-batched records during retries. 

[Gordon-C]

Unfortunately, we don't have that ability at this time.   But that's a great idea.   I'll create an enhancement request.