Skip to content

Update faq.mdx #24865

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 3, 2025
Merged

Update faq.mdx #24865

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2886b6c
Update faq.mdx
kathayl Sep 2, 2025
c72ccde
Update src/content/docs/browser-rendering/faq.mdx
kathayl Sep 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/content/docs/browser-rendering/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.