API Retries & Exponential Back-offs

Essential knowledge

Author:

Fluent Commerce staff

Changed on:

26 Oct 2023

Overview

Exponential backoff is a standard error handling policy for network communications such as the Fluent APIs.

Exponential backoff involves a client periodically retrying a failed request over an increasing amount of time.

Key points

Retries & Exponential Back-offs

For operations that create or update data, a check is recommended before retrying the API call to avoid unnecessary duplication.

Note

For example:

Order post fails with 500 Check if the order exists Retry after 1 second If still failing, retry after 10 seconds *If still failing, retry after 5 minutes

This is the recommended approach when dealing with server-side or network-related errors.

Warning

This approach is not recommended for client-side errors including authentication or invalid data (i.e. 300- and 400-level errors). These will always return the same error regardless of the retry or time delay.

Fluent Commerce staff

Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.

API Retries & Exponential Back-offs

Overview

Key points

Fluent Commerce staff

Building Blocks

By Type

Legal Resources