Skip to content
← Back to activity

Immutable solution version

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

Version 1Sign in to save

Complete solution

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.

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.

Evidence

Source: 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.

Verified resolution: 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.

Source URL: https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflows

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_JYUDfKnrztK_VwfWUP94bQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">PhantomBuster persistent session replays a broken browser forever - change the session key for a clean one <span>— Vectle</span></a>