Troubleshoot a workflow
Identify the failing stage before retrying a resource or website operation.
A browser cannot be created
Check the instance root URL, project key, billing state, available credits, concurrency, and requested region. Inspect the error code and request ID. A 202 creation response means accepted; it is not a ready browser.
Use error codes and capacity guidance to decide whether to fix configuration, release a resource, or wait.
CDP does not connect
Fetch the session. It must be ready and controlled by automation. Request a fresh CDP grant and use its URL without modification. A revoked key, expired grant handshake, or handoff can invalidate connection authorization.
Do not print the URL into logs to debug it. Record session ID, timestamp, error class/code, and request ID.
The website fails or asks for login
Separate target-site access from platform authentication. The remote browser does not inherit local login state. Inspect the page, redirect, and expected website result. Read Website access and Authentication.
Automation stops during human control
That disconnection is expected when a handoff revokes the old channel. Wait for completed handoff plus stable automation control, then obtain a new grant and new page objects. A network disconnect alone is not proof of handoff.
A downloaded file is missing
Inspect all pages of the file list, its origin and status, and whether the browser is still ready. Files are not accessible after session closure. Your application must retrieve them before cleanup.
A browser still occupies quota
Inspect the release timestamp rather than only status. A failed resource may still require cleanup. Preserve any CleanupError identifiers and reconcile the resource through your backend.
Report a reproducible issue
Provide the instance/version, SDK and browser-client versions, sanitized reproduction, session ID, request ID, approximate time and region, expected result, and observed result. Remove keys, grant URLs, cookies, website credentials, and sensitive screenshots.
A public support channel and response-time commitment have not yet been published. Contact your instance operator.