𝗪𝗵𝗲𝗻 𝘁𝗼 𝗤𝘂𝗮𝗿𝗮𝗻𝘁𝗶𝗻𝗲 𝗮 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗣𝗿𝗼𝗳𝗶𝗹𝗲

A browser profile lease solves concurrency. It tells you which worker owns a profile.

But after an automation failure, you face a new question.

Is this profile still safe to reuse?

Ownership and health are different. A worker can release a lease while leaving the profile in an unknown state. The profile may have new cookies, changed tokens, or unfinished forms.

If you give that profile to the next worker immediately, they inherit the damage.

This is why you need a quarantine state.

Quarantine is a post-failure state. It means you do not trust the account, session, or environment.

In browser automation, a profile is more than a folder. It carries: • Cookies and local storage • Login states and permissions • Proxy settings and language • Recent task history

If a run fails after login, the risk is high. You might face unexpected redirects, verification prompts, or expired sessions.

Do not quarantine every failure. You do not need it if:

  • The browser never launched
  • The profile was never opened
  • The worker failed before the lease
  • The run only touched public pages
  • The browser closed cleanly

Quarantine is vital when:

  • The worker crashed after opening the profile
  • The run reached an authenticated area
  • Session state or cookies changed
  • The failure happened near a non-idempotent action (like submitting a form)
  • The proxy or region changed during the run
  • Evidence is incomplete

A simple scheduler only checks if a profile is locked or unlocked. A professional system uses more states: • Available: Ready for work • Leased: In use • Cooldown: Needs a short break • Quarantined: Uncertainty created by failure • Needs Review: Requires human inspection • Retired: Do not use again

A quarantined profile must produce a decision. It should not be a forgotten holding area. Use it to capture the profile ID, the last URL, a screenshot, and the error reason.

Stop treating failed account environments as clean inputs. A lease prevents collisions. A quarantine prevents a chain of failures.

Source: https://dev.to/web4browser/when-a-browser-profile-should-be-quarantined-after-automation-failure-gpk