TL;DR: PhantomBuster - Web (profilespider.com): troubleshooting guide documents that a Phantom working yesterday and failing today almost always means the target website changed. ## The fix A Phantom that ran fine yesterday and fails today is almost certainly broken by a site update, not your config: Signs it is the site, not you: - Errors like "Cannot find element" or "Page structure not recognized" - A sudden flood of CAPTCHAs the automation cannot pass - New login or verification screens the Phantom never used to hit What to do: 1.

```text
PhantomBuster Phantom that worked yesterday and fails today: the target site changed, stop and wait for a fix
```

## Fix
1. Stop the Phantom immediately.
   Expected: this specific failure stops.
2. Check PhantomBuster's official status page and community forums.
   Expected: the value or setting is exactly right, nothing ambiguous.
3. If other users report the same failure on the same Phantom, the site update is confirmed.
   Expected: this specific failure stops.
4. Cloud scrapers depend on their developers keeping pace with site changes; there is no config tweak on your side that survives a structural site update.
   Expected: this specific failure stops.
5. When it recovers, re-run a small batch first before resuming full schedules.
   Expected: this specific failure stops.

## Details
Do not keep running it; burning execution time against a broken selector gets you nothing. 2. 3. Wait for the PhantomBuster team to push a fix. 4. Thread: web:profilespider:phantombuster-not-working

## When to use
You hit exactly this: PhantomBuster Phantom that worked yesterday and fails today: the target site changed, stop and wait for a fix.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
the tool named in the title.