Skip to content

Commit 200cae9

Browse files
kathaylToriLindsay
andauthored
Update limits.mdx (cloudflare#25070)
* Update limits.mdx new limits FAQ about extending browser timeout * Update limits.mdx * Update src/content/docs/browser-rendering/platform/limits.mdx Co-authored-by: ToriLindsay <[email protected]> * Update src/content/docs/browser-rendering/platform/limits.mdx Co-authored-by: ToriLindsay <[email protected]> * Update src/content/docs/browser-rendering/platform/limits.mdx --------- Co-authored-by: ToriLindsay <[email protected]>
1 parent fe91aa2 commit 200cae9

File tree

1 file changed

+10
-0
lines changed
  • src/content/docs/browser-rendering/platform

1 file changed

+10
-0
lines changed

src/content/docs/browser-rendering/platform/limits.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,3 +63,13 @@ If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/)
6363
file="manage-concurrency-faq"
6464
product="browser-rendering"
6565
/>
66+
67+
### Can I increase the browser timeout?
68+
69+
By default, a browser instance will time out after 60 seconds of inactivity. If you want to keep the browser open longer, you can use the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive) which allows you to extend the timeout to up to 10 minutes.
70+
71+
### Is there a maximum session duration?
72+
73+
There is no fixed maximum lifetime for a browser session as long as it remains active. By default, a browser will close after one minute of inactivity, but you can [extend this inactivity window](#can-i-increase-the-browser-timeout). Sessions will also be closed when Browser Rendering rolls out a new release.
74+
75+

0 commit comments

Comments
 (0)