How do I keep browser sessions alive across multiple cloud workers?
Keep session ownership outside an individual worker, and separate a running session from a saved profile. For AdsCrawl Cloud Browser, store the profile ID so later jobs can restart the same saved environment. This preserves supported profile state, not an indefinitely running browser or permanent login. Temporary Remote CDP sessions have a separate lifetime and do not automatically become saved profiles.
- In your job system, map each account to a profile ID and use a lease or lock so only one worker controls that profile at a time.
- Before continuing, query runtime status and verify the website's login state; API-key starts need an explicit valid proxy.
- After the job, stop the browser and confirm stopped before handing off ownership. Reauthenticate when the website requires it.