From 2886b6c3f4179608032cf3a25052d649952df8a5 Mon Sep 17 00:00:00 2001 From: Kathy <153706637+kathayl@users.noreply.github.com> Date: Tue, 2 Sep 2025 10:38:14 -0700 Subject: [PATCH 1/2] Update faq.mdx new FAQ Q --- src/content/docs/browser-rendering/faq.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/content/docs/browser-rendering/faq.mdx b/src/content/docs/browser-rendering/faq.mdx index 0177e1cf165933..e5770b93a6632f 100644 --- a/src/content/docs/browser-rendering/faq.mdx +++ b/src/content/docs/browser-rendering/faq.mdx @@ -94,3 +94,6 @@ If you are still running into concurrency limits you can [request a higher limit ### Is there a limit to how many requests a single browser session can handle? No, there is not a fixed limit on the number of requests per browser session. A single browser can handle multiple requests as long as it stays within the available compute and memory limits. + +### Do failed API calls, such as those that time out, add to billable browser hours? +No. If a request to the Browser Rendering REST API fails with a waitForTimeout error, the browser session is not charged. From c72ccdeb8d5a84a9787c97a4d1d2b46b3c183b8c Mon Sep 17 00:00:00 2001 From: Kathy <153706637+kathayl@users.noreply.github.com> Date: Wed, 3 Sep 2025 12:31:47 -0700 Subject: [PATCH 2/2] Update src/content/docs/browser-rendering/faq.mdx Co-authored-by: ToriLindsay --- src/content/docs/browser-rendering/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/browser-rendering/faq.mdx b/src/content/docs/browser-rendering/faq.mdx index e5770b93a6632f..084593fe92c931 100644 --- a/src/content/docs/browser-rendering/faq.mdx +++ b/src/content/docs/browser-rendering/faq.mdx @@ -96,4 +96,4 @@ If you are still running into concurrency limits you can [request a higher limit No, there is not a fixed limit on the number of requests per browser session. A single browser can handle multiple requests as long as it stays within the available compute and memory limits. ### Do failed API calls, such as those that time out, add to billable browser hours? -No. If a request to the Browser Rendering REST API fails with a waitForTimeout error, the browser session is not charged. +No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.