diff --git a/articles/active-directory-b2c/api-connectors-overview.md b/articles/active-directory-b2c/api-connectors-overview.md
index e63b2348c301e..20a11b8f69c2a 100644
--- a/articles/active-directory-b2c/api-connectors-overview.md
+++ b/articles/active-directory-b2c/api-connectors-overview.md
@@ -87,7 +87,7 @@ Using Azure AD B2C, you can add your own business logic to a user journey by cal
 ![Diagram of a RESTful service claims exchange](media/api-connectors-overview/restful-service-claims-exchange.png)
 
 > [!NOTE]
-> HTTP requests may be cancelled if there is a slow or no response from the RESTful service to Azure AD B2C. The default timeout is 10 seconds and the default retry count is one (meaning there are 2 tries in total).
+> HTTP requests may be cancelled if there is a slow or no response from the RESTful service to Azure AD B2C. The default timeout is 10 seconds for custom policies and 5 seconds for user flows. The default retry count is one (meaning there are 2 tries in total).
 
 ## Calling a RESTful service