Skip to content

Commit b8803da

Browse files
kathaylToriLindsay
andauthored
Update limits.mdx (#25947)
update max session duration FAQ Co-authored-by: ToriLindsay <[email protected]>
1 parent d177ca4 commit b8803da

File tree

1 file changed

+3
-1
lines changed
  • src/content/docs/browser-rendering/platform

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,9 @@ By default, a browser instance will time out after 60 seconds of inactivity. If
7474

7575
### Is there a maximum session duration?
7676

77-
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.
77+
There is no fixed maximum lifetime for a browser session as long as it remains active. By default, Browser Rendering closes sessions after 1 minute of inactivity to prevent unintended usage. You can [increase this inactivity timeout](/browser-rendering/platform/puppeteer/#keep-alive) to up to 10 minutes.
78+
79+
If you need sessions to remain open longer, keep them active by sending a command at least once within your configured inactivity window (for example, every 10 minutes). Sessions also close when Browser Rendering rolls out a new release.
7880

7981
### I upgraded from the Workers Free plan, but I'm still hitting the 10-minute per day limit. What should I do?
8082

0 commit comments

Comments
 (0)