From fd7c56da38e6952559b88969dee84ad47bc1ae7e Mon Sep 17 00:00:00 2001 From: Csilla Kisfaludi <55664408+aisz0811@users.noreply.github.com> Date: Mon, 30 Jun 2025 16:37:10 +0200 Subject: [PATCH 1/4] Update troubleshooting.mdx --- website/docs/advanced/troubleshooting.mdx | 24 +++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/website/docs/advanced/troubleshooting.mdx b/website/docs/advanced/troubleshooting.mdx index 3da534c85..5b8cb24dd 100644 --- a/website/docs/advanced/troubleshooting.mdx +++ b/website/docs/advanced/troubleshooting.mdx @@ -4,19 +4,19 @@ title: Troubleshooting description: This section helps you troubleshoot your issues. It's a good idea to double check these before contacting support. --- -The following issues were reported by customers. We collected what we learned and the possible solutions. +The following issues were reported by customers. We've collected what we've learned and provided possible solutions. ## Long response times and connection issues -First, you can verify on the [Service Status Monitor](https://status.configcat.com) whether ConfigCat is up and running or there is a planned maintenance. +First, check the [Service Status Monitor](https://status.configcat.com) to see if ConfigCat is up and running or if there any planned maintenance. ### General SDK Checklist -1. It might be a good idea to update the ConfigCat SDK to the latest version. -1. Check if you configured the [Data Governance](../advanced/data-governance.mdx) functionality properly. -1. Singleton: We strongly recommend using the ConfigCat SDK as a Singleton. Initializing the SDK over and over again can cause serious performance issues in production. If you want to use multiple SDK Keys in the same application, create only one _ConfigCat Client_ per SDK Key. +1. Make sure you're using the latest version of the ConfigCat SDK. +1. Check if you've configured the [Data Governance](../advanced/data-governance.mdx) functionality correctly. +1. Singleton: We strongly recommend using the ConfigCat SDK as a singleton. Initializing the SDK multiple times can cause serious performance issues in production. If you need to use multiple SDK Keys in the same application, create only one _ConfigCat Client_ per SDK Key. 1. Are you using the proper polling mode for your use case? Details on polling modes in the [SDK Docs](../sdk-reference/overview.mdx). -1. Might be a too frequent `Auto Polling` interval. Please check the [SDK Docs](../sdk-reference/overview.mdx). +1. Your `Auto Polling` interval might be too frequent Please check the [SDK Docs](../sdk-reference/overview.mdx). 1. In `Manual Polling` mode, it could be a too frequent `forceRefresh()` call in your code, making the SDK download the config JSON often. 1. You can try one of our lightweight sample applications to rule out local issues. Find in the [repository of each SDK](https://github.com/configcat). @@ -26,17 +26,17 @@ First, you can verify on the [Service Status Monitor](https://status.configcat.c Please, **do not load test** the ConfigCat production infrastructure without our consent. ::: -1. You can check the response times manually by navigating to `https://cdn.configcat.com/ping.txt` and opening your browser's network tab. -1. Does the machine/server your code runs on has access to the above address? +1. You can check response times manually by navigating to `https://cdn.configcat.com/ping.txt` and opening your browser's network tab. +1. Does the machine/server running your code have access to the above address? 1. You might need to whitelist the following addresses in your firewall: `cdn.configcat.com`, `cdn-eu.configcat.com`, `cdn-global.configcat.com`. --- ## Too many requests error in Angular -The problem was caused by Angular's Hot Module Replacement functionality during development. The wrapper class, which contained the auto polling ConfigCat SDK was edited, and the Hot Module Replacement reinitialized the whole class without releasing the old, replaced module's Auto Polling timer. -We believe that this is a really rare case, it could happen only during development. +This issue can occure due to Angular's Hot Module Replacement functionality during development. The wrapper class containing the Auto Polling ConfigCat SDK is edited, the Hot Module Replacement can reinitialize the whole class without releasing the old, replaced module's Auto Polling timer. +We believe that this is a rare edge case that only happens during development. -## Python Auto polling issue with uWSGI web server +## Python Auto Polling issue with uWSGI web server -The Python SDK's Auto polling mode utilizes its polling job in a `threading.Thread` object. If you are running your application behind an uWSGI web server, the auto polling mode may not work as expected because the uWSGI web server disables Python's threading by default. Please [enable threading](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#enable-threads) or switch to another polling mode in this case. +The Python SDK's Auto Polling mode utilizes its polling job in a `threading.Thread` object. If you run your application behind an uWSGI web server, the Auto Polling mode may not work as expected because the uWSGI web server disables Python's threading by default. Please [enable threading](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#enable-threads) or switch to another polling mode in this case. From 2aeb9018abfcfbc3e0de11f4e12818151881f851 Mon Sep 17 00:00:00 2001 From: adams85 <31276480+adams85@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:07:50 +0200 Subject: [PATCH 2/4] Update website/docs/advanced/troubleshooting.mdx --- website/docs/advanced/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/troubleshooting.mdx b/website/docs/advanced/troubleshooting.mdx index 5b8cb24dd..fc2a9e923 100644 --- a/website/docs/advanced/troubleshooting.mdx +++ b/website/docs/advanced/troubleshooting.mdx @@ -4,7 +4,7 @@ title: Troubleshooting description: This section helps you troubleshoot your issues. It's a good idea to double check these before contacting support. --- -The following issues were reported by customers. We've collected what we've learned and provided possible solutions. +The following issues were reported by customers. We've collected what we've learned and provided the possible solutions below. ## Long response times and connection issues From 83ff12cc6ca426d567fef4776a374e8358eb6d3f Mon Sep 17 00:00:00 2001 From: adams85 <31276480+adams85@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:08:32 +0200 Subject: [PATCH 3/4] Update website/docs/advanced/troubleshooting.mdx --- website/docs/advanced/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/troubleshooting.mdx b/website/docs/advanced/troubleshooting.mdx index fc2a9e923..e173f41be 100644 --- a/website/docs/advanced/troubleshooting.mdx +++ b/website/docs/advanced/troubleshooting.mdx @@ -8,7 +8,7 @@ The following issues were reported by customers. We've collected what we've lear ## Long response times and connection issues -First, check the [Service Status Monitor](https://status.configcat.com) to see if ConfigCat is up and running or if there any planned maintenance. +First, check the [Service Status Monitor](https://status.configcat.com) to see if ConfigCat is up and running or if there is any planned maintenance. ### General SDK Checklist From c11d472a5c23159833525b3c9d2989913d0fa347 Mon Sep 17 00:00:00 2001 From: adams85 <31276480+adams85@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:19:15 +0200 Subject: [PATCH 4/4] Update website/docs/advanced/troubleshooting.mdx --- website/docs/advanced/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/troubleshooting.mdx b/website/docs/advanced/troubleshooting.mdx index e173f41be..b67331900 100644 --- a/website/docs/advanced/troubleshooting.mdx +++ b/website/docs/advanced/troubleshooting.mdx @@ -39,4 +39,4 @@ We believe that this is a rare edge case that only happens during development. ## Python Auto Polling issue with uWSGI web server -The Python SDK's Auto Polling mode utilizes its polling job in a `threading.Thread` object. If you run your application behind an uWSGI web server, the Auto Polling mode may not work as expected because the uWSGI web server disables Python's threading by default. Please [enable threading](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#enable-threads) or switch to another polling mode in this case. +The Python SDK's Auto Polling mode runs its polling job in a `threading.Thread` object. If you run your application behind an uWSGI web server, the Auto Polling mode may not work as expected because the uWSGI web server disables Python's threading by default. Please [enable threading](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#enable-threads) or switch to another polling mode in this case.