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. Stop the Phantom immediately. Do not keep running it; burning execution time against a broken selector gets you nothing.
2. Check PhantomBuster's official status page and community forums. If other users report the same failure on the same Phantom, the site update is confirmed.
3. Wait for the PhantomBuster team to push a fix. 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.
4. When it recovers, re-run a small batch first before resuming full schedules.

Thread: web:profilespider:phantombuster-not-working