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
We recently made it so that flow starts and broadcasts are throttled based on the outbox - their batch tasks of 100 sit in a queue throttled by the outbox size. But timeouts and expirations go straight into the contact handler queues. If you start a lot of contacts in a flow that begins with a wait with a timeout, you'll get 1) a big handler queue and handler latency 2) the potential for a lot of outgoing messages being created without any throttling against the outbox.
The text was updated successfully, but these errors were encountered:
We recently made it so that flow starts and broadcasts are throttled based on the outbox - their batch tasks of 100 sit in a queue throttled by the outbox size. But timeouts and expirations go straight into the contact handler queues. If you start a lot of contacts in a flow that begins with a wait with a timeout, you'll get 1) a big handler queue and handler latency 2) the potential for a lot of outgoing messages being created without any throttling against the outbox.
The text was updated successfully, but these errors were encountered: