Skip to content

Batch/retry system updates
Compare
Choose a tag to compare
@tdumitrescu tdumitrescu released this 12 Nov 23:18
· 133 commits to master since this release
v2.42.0
d192aef

The batch_requests configuration introduced in v2.36.0 is now on by default for all projects. To turn it off, initialize the SDK with the explicit option {batch_requests: false}. Individual track() calls can still bypass the queueing system with the flag {send_immediately: true}.

In addition, this release contains several updates/fixes for send/retry behavior:

  • Requests blocked on the client side (e.g., via an adblocker) are no longer retried.
  • 429 (rate-limited) responses from the API are retried with backoff (in batch mode)
  • The deprecated unload event is no longer used to determine when to flush queues via sendBeacon on page close; this is now detected via the more modern alternatives visibilitychange and pagehide.
Assets 2