You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/browser-rendering/faq.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,4 +96,4 @@ If you are still running into concurrency limits you can [request a higher limit
96
96
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.
97
97
98
98
### Do failed API calls, such as those that time out, add to billable browser hours?
99
-
No. If a request to the Browser Rendering REST API fails with a waitForTimeout error, the browser session is not charged.
99
+
No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.
0 commit comments