Rate limiting and retry policy for streaming destinations built with Destination SDK

Partner-built destinations can return various errors and have different rate limiting policies. This page explains how Experience Platform handles different types of errors returned by streaming destinations.

When configuring a destination using Destination SDK, you can select between two aggregation types - best effort aggregation and configurable aggregation. Depending on the aggregation type that you select, read below how Experience Platform handles errors and rate limitations.

Best effort aggregation best-effort-aggregation

Experience Platform retries calls that return the following HTTP response codes: 403, 408, 409, 429, 500, 502, 503, 504. Two retries are performed at the following intervals:

Experience Platform does not retry calls that return other HTTP response codes, such as 400 (Bad Request). If the call still fails after both retry attempts, Experience Platform drops the activation and does not reattempt it.

You can request a different retry policy for specific dataflows by contacting Customer Support.

Configurable aggregation configurable-aggregation

In the case of destination platforms set up with configurable aggregation, Experience Platform distinguishes between the error type returned by your platform:

Retry approach described retry-approach

The Experience Platform approach for configurable aggregation is described below. This example assumes that Experience Platform sends data to a destination platform that starts returning 429 error codes if it receives more than 50k requests per minute:

Next steps next-steps

You now know how Experience Platform handles errors and rate limiting from destination platforms, depending on the aggregation policy you selected when you configured your streaming destination. Next, you can review the following documentation: