From 77b5e624c556c66b3d59d7a03709c2e9d514b033 Mon Sep 17 00:00:00 2001 From: Melinda Fekete Date: Fri, 11 Jul 2025 13:13:30 +0200 Subject: [PATCH] Update website/docs/troubleshooting.mdx Co-authored-by: Simon Hornby --- website/docs/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/troubleshooting.mdx b/website/docs/troubleshooting.mdx index a03eaceaa4..d331d50931 100644 --- a/website/docs/troubleshooting.mdx +++ b/website/docs/troubleshooting.mdx @@ -16,7 +16,7 @@ If a feature flag isn't being returned by the Frontend API or Edge, or if users - Confirm that the feature flag has been **enabled** in the specific environment your client application is using. (ref: [enabling a feature flag](/reference/feature-toggles)) #### SDK `ready` event (frontend clients) -- Ensure your application, especially frontend clients, waits for the SDK to emit the `ready` event before calling `isEnabled('feature-flag')` or attempting to get variant information. Calling these functions too early might mean the client hasn't yet received the latest flag configurations from the server. +- Ensure your application, especially frontend clients, waits for the SDK to emit the `ready` event before calling `isEnabled('feature-flag')` or `getVariant('feature-flag')`. Calling these functions too early might mean the client hasn't yet received the latest flag configurations from the server. ### Token configuration