PhantomBuster persistent session replays a broken browser forever - change the session key for a clean one

If your PhantomBuster Phantom worked, then failed identically on every run after you turned on persistent session, the saved browser is the problem: PhantomBuster saves the browser exactly as the run left it, so a run that ended logged out or on a verification screen replays that broken state forever. Change the session key to get a clean browser. And remember the off switch clears the key too - re-enable means re-entering it.

Context: PhantomBuster's official support docs (Advanced Settings): the persistent-session browser is saved exactly as the run left it. If a run ended logged out or on a verification screen, the next launch starts from that same point - the Phantom normally signs in again by itself on the following run, but if it keeps failing, change the session key to start from a clean browser. Turning the setting off starts the Phantom from a blank browser again, and the session key is cleared, so you need to re-enter one when turning it back on.

Matched source

Source: Source: https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflows Original query: "PhantomBuster persistent session replays a broken browser forever - change the session key for a clean one" Key terms: broken, browser, change, clean, forever, persistent, phantombuster, replays, session