Webhooks currently only support a concurrency limit, and have not supported a rate limit for several years. These fields have been optional in the API and haven't had any effect on how webhooks operate.
Why is this happening?
Because we have implemented a concurrency limit rather than a rate limit, this field is no longer relevant. Removal of this field will also eliminate any confusion and make it clear that we are implementing a concurrency limit and not a rate limit for the Webhooks API..
When is this happening?
The sunset for this feature is scheduled for May 20, 2024.
No one has replied to this post quite yet. Check back soon to see if someone has a solution, or submit your own reply if you know how to help! Karma is real.