Skip to content

Commit 1423e44

Browse files
authored
Update limits.mdx
added Limits FAQ
1 parent a56e798 commit 1423e44

File tree

1 file changed

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

1 file changed

+15
-0
lines changed

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

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,18 @@ By default, a browser will time out if it does not get any [devtools](https://ch
5252
## Note on concurrency
5353

5454
While the limits above define the maximum number of concurrent browser sessions per account, in practice you may not need to hit these limits. Browser sessions close automatically—by default, after 60 seconds of inactivity or upon task completion—so if each session finishes its work before a new request comes in, the effective concurrency is lower. This means that most workflows do not require very high concurrent browser limits.
55+
56+
## FAQ
57+
58+
### I upgraded from the Workers Free plan, but I'm still hitting the 10-minute per day limit. What should I do? --> LIMITS PAGE
59+
60+
If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/) but still encounter the 10-minute per day cap, redeploy your Worker to ensure your usage is correctly associated with the new plan.
61+
62+
### How can I manage concurrency and session isolation with Browser Rendering?
63+
64+
If you are hitting concurrency [limits](/browser-rendering/platform/limits/#workers-paid), or want to optimize concurrent browser usage with the [Workers Binding method](/browser-rendering/workers-bindings/), here are a few tips:
65+
66+
- Optimize with tabs or shared browsers: Instead of launching a new browser for each task, consider opening multiple tabs or running multiple actions within the same browser instance.
67+
- [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.
68+
69+
If you are still running into concurrency limits you can [request a higher limit](https://forms.gle/CdueDKvb26mTaepa9).

0 commit comments

Comments
 (0)