',
+ flagConfigurationFetch: withTimeout(globalThis.fetch, 1_500),
});
// Set the evaluation context
@@ -226,6 +228,30 @@ The web provider also supports these optional settings:
| `flaggingProxy` | unset | Fetch flags through a proxy instead of `site`. |
| `customHeaders` | unset | Add headers to flag-fetch requests. |
| `overwriteRequestHeaders` | `false` | Replace default request headers with `customHeaders`. |
+| `flagConfigurationFetch` | `globalThis.fetch` | Provide a Fetch-compatible implementation for flag configuration requests. |
+
+### Bound flag configuration requests
+
+The browser provider does not add a timeout or retries by default. Use `withTimeout` and `withRetry` to bound each request attempt and retry transient failures:
+
+{{< code-block lang="javascript" >}}
+import { DatadogProvider, withRetry, withTimeout } from '@datadog/openfeature-browser';
+
+const provider = new DatadogProvider({
+ // Other provider options...
+ flagConfigurationFetch: withRetry(withTimeout(globalThis.fetch, 1_500), 2),
+});
+{{< /code-block >}}
+
+`withTimeout(fetch, timeoutMs)`
+: Sets the timeout in milliseconds for each request attempt, including the complete response-body download. Set the timeout to `0` to disable the timer. Accepted values are non-negative integers up to `2_147_483_647`.
+
+`withRetry(fetch, retryCount)`
+: Sets the number of retries after the initial request. Set the retry count to `0` to disable retries. Accepted values are integers from `0` to `10`. Retries cover Fetch `TypeError` failures, timeout errors, HTTP 408, and HTTP 5xx responses. Caller cancellation and HTTP 429 responses are not retried. Retries use randomized exponential backoff capped at 30 seconds. For HTTP 503, a valid `Retry-After` value up to 30 seconds is a minimum delay before the backoff. A response that requests a longer delay is not retried. Browsers report network, CORS, and CSP failures as `TypeError`, so the wrapper cannot separate these causes.
+
+In the example, `withTimeout` is inside `withRetry`. Therefore, each attempt has its own 1,500-millisecond timeout.
+
+The `flagConfigurationFetch` option applies only to flag configuration requests. It does not affect exposure, aggregated flag evaluation, or RUM telemetry requests.
## Override flags in your browser
diff --git a/hugo/content/en/feature_flags/client/unity.md b/hugo/content/en/feature_flags/client/unity.md
index 270aa8ec788..591176981c9 100644
--- a/hugo/content/en/feature_flags/client/unity.md
+++ b/hugo/content/en/feature_flags/client/unity.md
@@ -52,7 +52,9 @@ After initializing Datadog, enable `Flags` to attach it to the current Datadog U
{{< code-block lang="csharp" >}}
using Datadog.Unity.Flags;
-DdFlags.Enable();
+DdFlags.Enable(new FlagsConfiguration(
+ assignmentRequestTimeoutSeconds: 1,
+ assignmentRequestRetryCount: 0));
{{< /code-block >}}
You can also pass a configuration object; see [Advanced configuration](#advanced-configuration).
@@ -203,12 +205,35 @@ The `DdFlags.Enable()` API accepts optional configuration with options listed be
{{< code-block lang="csharp" >}}
DdFlags.Enable(new FlagsConfiguration(
+ assignmentRequestTimeoutSeconds: 1,
+ assignmentRequestRetryCount: 2,
trackExposures: true,
trackEvaluations: true,
evaluationFlushIntervalSeconds: 10.0f
));
{{< /code-block >}}
+`assignmentRequestTimeoutSeconds`
+: Timeout in seconds for each flag assignment request, including the complete response-body download. The SDK does not add a timeout by default. Set a positive value to enable the timeout; `0` leaves it disabled.
+
+`assignmentRequestRetryCount`
+: Number of retries after the initial flag assignment request. The default is `0`, so the SDK makes only the initial request unless you opt in to retries. Accepted values are from `0` to `10`. Retries cover selected transient network errors, timeouts, HTTP 408, and HTTP 5xx responses. Cancellation, HTTP 429, generic I/O errors, permanent protocol errors, and TLS failures are not retried. Retries use randomized exponential backoff capped at 30 seconds. For HTTP 503, a valid `Retry-After` value up to 30 seconds is a minimum delay before the backoff. A response that requests a longer delay is not retried.
+
+Assignment request timeout and retry settings apply only to requests that fetch flag assignments. They do not affect exposure, aggregated flag evaluation, or RUM telemetry requests.
+
+For lower-level transport control, compose an assignment-only transport:
+
+{{< code-block lang="csharp" >}}
+var assignmentTransport = AssignmentRequestTransports.Default
+ .WithTimeout(1)
+ .WithRetry(2);
+
+DdFlags.Enable(new FlagsConfiguration(
+ assignmentRequestTransport: assignmentTransport));
+{{< /code-block >}}
+
+A supplied `assignmentRequestTransport` is used verbatim and replaces the scalar timeout and retry settings. The helpers use fully buffered immutable responses, create a fresh native request for each retry, and apply only to assignment requests. The SDK owns its native requests; the application retains ownership of a custom transport and its resources.
+
`trackExposures`
: When `true` (default), the SDK automatically records an _exposure event_ when a flag is evaluated. These events contain metadata about which flag was accessed, which variant was served, and under what context. They are sent to Datadog so you can later analyze feature adoption. Set to `false` to disable exposure tracking.
diff --git a/hugo/content/en/getting_started/feature_flags/_index.md b/hugo/content/en/getting_started/feature_flags/_index.md
index b5ad7b7b206..846204dbf91 100644
--- a/hugo/content/en/getting_started/feature_flags/_index.md
+++ b/hugo/content/en/getting_started/feature_flags/_index.md
@@ -86,6 +86,8 @@ You can set up Feature Flags automatically with the Client SDKs do not add a flag assignment request timeout or retry by default, so the underlying platform transport remains authoritative. Configure a timeout of at most 1,500 milliseconds when initialization must finish within a known period. Retries cover transient network errors, timeouts, HTTP 408, and HTTP 5xx responses. They use randomized exponential backoff capped at 30 seconds. For HTTP 503, a valid Retry-After value up to 30 seconds is a minimum delay before the backoff. A response that requests a longer delay is not retried. Mobile SDKs do not retry cancellation, HTTP 429, generic I/O errors, permanent protocol errors, or TLS failures. Browser Fetch reports several failures as TypeError and cannot separate these causes. See the client SDK guides for platform-specific timeout, retry, and transport APIs.
+
{{< tabs >}}
{{% tab "JavaScript browser" %}}
@@ -100,7 +102,7 @@ Then, add the following to your project to initialize the SDK:
{{< site-region region="gov,gov2" >}}Browser Feature Flags are not supported for the selected
Datadog site ({{< region-param key="dd_site_name" >}}).