If your X/Twitter Phantom returns an "Error while loading data" message, it means PhantomBuster couldn't load data from X/Twitter. This is almost always caused by X/Twitter updating their code or page structure, not by anything in your setup. Wait a few hours and retry - if the issue persists, contact Customer Care so we can investigate on our end.
Why you’re seeing this
This error means PhantomBuster couldn’t load data from X/Twitter. It usually happens when X/Twitter updates its code or page structure, which can temporarily affect how data is loaded.
It can also occur if:
- Your X/Twitter session cookie has expired or become invalid
- X/Twitter is experiencing a temporary platform outage
- The specific page the Phantom is trying to load has been removed or restricted
How to fix it
Wait and retry
Since this error is most commonly caused by temporary X/Twitter code changes, wait a few hours and relaunch the Phantom. If the Phantom is scheduled to run repeatedly, it will retry automatically on the next launch.
Check your session cookie
Even though this error is usually platform-side, it's worth verifying your X/Twitter session is still valid. Open X/Twitter in your browser and confirm you're logged in. If your session has expired, reconnect your account in the Phantom setup.
Test manually
Visit the X/Twitter page your Phantom is trying to load (e.g. a profile, search, or timeline). If X/Twitter shows an error or loads incorrectly for you too, the issue is on their side, wait for them to resolve it.
Frequently asked questions
Should I retry later?
Yes. Many X/Twitter code changes are temporary or get rolled back. Waiting a few hours and relaunching often resolves the issue without any action on your end.
Does this affect all X/Twitter Phantoms?
Not necessarily. It depends on which part of X/Twitter's code changed. Some Phantoms may be affected while others continue working normally.
Can an expired session cookie cause this?
It's possible but unlikely to be the primary cause. If the error started appearing suddenly across multiple runs, it's more likely a platform change. But checking your cookie is a quick step worth taking.
Still seeing the error
This issue isn't caused by your setup and may require a PhantomBuster-side fix. Get in touch with our Customer Care Team so we can review and resolve the issue. Include:
- The Phantom name and link
- A screenshot of the error in the output
- The launch log
- When the error first started appearing
- Whether it affects every run or only some