Skip to content

Commit 0af7a3c

Browse files
authored
Update limits.mdx
new limits FAQ about extending browser timeout
1 parent 6079b14 commit 0af7a3c

File tree

1 file changed

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

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,3 +67,7 @@ If you are hitting concurrency [limits](/browser-rendering/platform/limits/#work
6767
- [Reuse sessions](/browser-rendering/workers-bindings/reuse-sessions/): You can optimize your setup and decrease startup time by reusing sessions instead of launching a new browser every time. If you are concerned about maintaining test isolation (for example, for tests that depend on a clean environment) we recommend using [incognito browser contexts](https://pptr.dev/api/puppeteer.browser.createbrowsercontext), which isolate cookies and cache with other sessions.
6868

6969
If you are still running into concurrency limits you can [request a higher limit](https://forms.gle/CdueDKvb26mTaepa9).
70+
71+
### Can I increase the browser timeout?
72+
73+
By default, a browser instance will time out after 60 seconds of inactivity. If you’d like 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.

0 commit comments

Comments
 (0)