Skip to content

Connected Content retries

Because Connected Content relies on receiving data from APIs, there is the possibility that an API is intermittently unavailable while Braze makes the call. In this case, Braze supports retry logic to re-attempt the request using exponential backoff.

To enable retries, add :retry in the Connected Content call, as shown in the following code snippet:

{% connected_content :retry %}
{% connected_content :save my_content :basic_auth auth_name :retry %}

If the API call fails and this is enabled, Braze will retry the call while respecting the rate limit you set for each resend. Braze will move any failed messages to the back of the queue and add additional minutes, if necessary, to the total minutes it would take to send your message.

If a retried attempt succeeds, the message is sent and no further retries are attempted for that message. If the Connected Content call errors out 5 times, the message is aborted similar to if an abort message tag was triggered.

New Stuff!