FAQ

Browser spin-up time

Non-standard configuration can affect browser spin-up time. Settings like non-default viewport sizing, extensions, or Profiles may increase the time it takes for a browser to become ready.

Standard configuration includes:

• Headful and headless browsers
• Stealth mode both enabled and disabled

If you're experiencing slower-than-expected browser creation times, review your configuration to identify any non-standard settings that may be contributing to the delay.

Connection notes

• CDP connections are meant to be long-lived but may eventually close. Websocket connections typically can remain active for up to 1 hour, after which they may close automatically. Browser sessions themselves are unaffected—reconnect to the same cdp_ws_url to continue using the browser.
• Browsers persist independently of CDP. Depending on your timeout configuration, it will continue running even if the CDP connection closes. You can reconnect to the same cdp_ws_url if you're unexpectedly disconnected.
• We recommend implementing reconnect logic, as network interruptions or lifecycle events can cause CDP sessions to close. Detect disconnects and automatically re-establish a CDP connection when this occurs.

Bot detection varies by site

Websites differ widely in how aggressively they detect and challenge automation, and the same site can behave differently depending on how you approach it. Rather than a fixed list of "supported" and "unsupported" sites, it's more useful to understand what drives that friction and how to reduce it.

What tends to increase bot-detection friction:

• High-volume or high-concurrency scraping — many requests from the same exit IP raise the block rate. Spread load across proxies and reuse Profiles.
• Aggressive detection vendors (Cloudflare, DataDome, PerimeterX, Imperva, Akamai) — these can challenge even anonymous page loads. Enable stealth mode and consider computer controls for more human-like interaction.

For workflows behind a login, Managed Auth handles the login flow and keeps sessions persistently authenticated across runs.