When WebHooks match Issues with too much data or history, performance may be impacted as the Thread will read too much data from the DB and serialize it all into the request body (payload).
See How to find the Issues with most data in Jira for more.

Many customers need to post the Issue data to the WebHook URL but are only interested in the "most recent" updates, not the entire Issue's history since it's creation — like a "delta".

It'd be helpful to allow WebHooks to be configured with a time threshold so only historical data within that threshold would be read and serialized:

• Change records / Issue History (from changegroup and changeitem tables)
• Comments history (ref. JRASERVER-67459)
• Maybe Issue Links? (if possible to fetch only the links created within the time threshold)

This won't be technically the "delta" many integrations would expect but it won't impact the system as much as fetching all the data every time.