You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company receives and processes getstream webhooks for a variety of reasons, and normally the system works well. However, when we use the campaigns feature to send a message to our entire user base (~100K users), the server that processes webhooks gets hit with a massive traffic spike due to the fact that so many messages are sent within a short period of time. This causes a bunch of load-related problems -- database connection issues, timeouts or rate limit errors on other third-party services, etc.
It would be great if we could disable webhooks for campaigns, possibly by adding a disable_webhooks option to the api call that triggers the campaign.
Thanks much :)
The text was updated successfully, but these errors were encountered:
My company receives and processes getstream webhooks for a variety of reasons, and normally the system works well. However, when we use the campaigns feature to send a message to our entire user base (~100K users), the server that processes webhooks gets hit with a massive traffic spike due to the fact that so many messages are sent within a short period of time. This causes a bunch of load-related problems -- database connection issues, timeouts or rate limit errors on other third-party services, etc.
It would be great if we could disable webhooks for campaigns, possibly by adding a
disable_webhooks
option to the api call that triggers the campaign.Thanks much :)
The text was updated successfully, but these errors were encountered: