How to Fix Phantombuster "Error During Loading of Chat Widget"
Phantombuster documents this one, and the documented fix is mostly to wait. The expensive part is a Phantom left looping against it, burning execution time on attempts that cannot succeed.
You launch a LinkedIn Message Sender Phantom, the queue sits there, and the log reads Error during loading of chat widget. No message went out, nothing says why, and the Phantom keeps trying.
Two things are worth knowing before you change anything. Phantombuster documents this error, so there is a known answer rather than a mystery. And the expensive part is not the failed send: it is a Phantom left running against a failure it cannot recover from, burning execution time on every attempt. Pausing it is the first move, not the last.
Which error you actually have
Phantombuster's Message Sender can fail for several unrelated reasons, and they all present as messages that did not send. The error text is the only thing that separates them, which makes reading it properly the highest-value thirty seconds in this whole process.
| What the log says | What it means | What to do |
|---|---|---|
| Error during loading of chat widget | LinkedIn's chat interface did not initialise in the browser | Pause, check ongoing issues, wait a few minutes, relaunch |
| Missing Send button, or Premium account needed | LinkedIn shows no Send button on that profile at all | Nothing to fix: they are not a 1st-degree connection |
| InMail required | A direct message is not available, LinkedIn wants an InMail | Connect first, or use an InMail if you have credits |
| Follow-ups never sent | The connection was not accepted, or they already replied | Nothing: the workflow has not reached that step yet |
The distinction that saves the most time is between the first row and the second. The chat widget error is environmental and usually clears itself. A missing Send button is not an error in any useful sense: LinkedIn only lets you message someone directly if they are a 1st-degree connection, or if they have the Open Profile feature enabled. No cookie refresh, cache clear or browser change will produce a Send button that LinkedIn is not rendering.
As for the chat widget itself, the causes are all environmental: a temporary problem on LinkedIn's side, stale cache or cookies preventing the chat module from rendering, a connection too slow for the widget to finish loading, or a lapsed session so the chat frame cannot authenticate. None of them are Phantombuster's doing, and none of them are fixed by trying harder.
The fix, in order
Cheapest first, and the first two are free.
Pause the Phantom
Stop the job before anything else. You are not preventing a send that would have worked, you are stopping repeated failures from consuming execution time. It also gives you a stable picture of the logs instead of a file that keeps growing while you read it.
Check Phantombuster's Ongoing Issues page
Phantombuster maintains a page for current problems with Phantoms. If the chat widget error is listed there, you are done: the answer is to wait, and nothing you do to your own setup will change the outcome. Thirty seconds here saves an hour of clearing caches for a problem that was never on your side.
Wait a few minutes, then relaunch
This really is the documented fix for most occurrences. The error is usually temporary, so a short pause and a relaunch resolves it. Resist the urge to change five things at once before trying this, because if it works you will not know which of the five mattered and you will repeat the whole ritual next time.
Refresh the session cookie and clear LinkedIn cache
If it survives a relaunch, log into LinkedIn in a browser, copy the current li_at session cookie and paste it into the Phantom's settings. Then clear your LinkedIn cache and cookies and restart the browser. A lapsed session stops the chat frame authenticating, and stale cached data stops the module rendering, so this addresses two of the four causes at once.
Update the browser and the connection
Run a current stable Chrome or Firefox, which is what Phantombuster expects. And avoid sending across a dropping VPN or unreliable wifi: the widget can time out before it has finished loading, and an intermittent connection produces exactly the intermittent failure that is hardest to attribute.
Keeping sends reliable
Four habits that remove most of these before they happen.
- Read the error text before you act. Half of the message sender failures people call the chat widget error are a missing Send button, which has a completely different answer and is not fixable at all.
- Keep the session fresh. A lapsed li_at is behind several distinct Phantombuster failures, so refreshing it when you notice any of them is usually worth the thirty seconds.
- Run on a stable connection and a current browser. Neither is glamorous, and together they cover the two causes that produce intermittent, hard-to-reproduce failures.
- Check the ongoing issues page as a reflex, not a last resort. It is the only one of these four that can tell you the problem is definitively not yours.
What none of this does is make LinkedIn's chat interface load faster. It stops you spending execution time and attention on a failure whose documented fix is usually to wait.
If the session cookie turns out to be the culprit, we went through that failure in detail in how to fix the Phantombuster expired session cookie error.
Sending without a browser to babysit
Step back and the shape of the problem is a browser automating a web interface. The chat widget has to render, the session has to hold, the connection has to stay up, and the machinery is visible to you because when any part of it slips you are the one reading the log.
ReactIn sends from our servers rather than from a browser session you maintain, so there is no widget to initialise on your side and no execution time to spend on a failed attempt. You connect the account once and campaigns run whether or not your machine is on.
Two things we are not going to claim, because both would be false. We are not immune to LinkedIn: if LinkedIn has a problem, or changes its interface, that reaches every tool including ours. And we do not quietly keep a session alive forever behind your back, because an account sometimes genuinely needs you to re-authenticate, and a vendor promising you will never be asked again is promising something you should not want.
The honest limit: LinkedIn's own rules decide who you can message. A person who is not a 1st-degree connection cannot be messaged directly through ReactIn either, for the same reason the Send button is missing in Phantombuster. That constraint is LinkedIn's, and no tool removes it.
For a feature-by-feature view of the two, see our ReactIn vs Phantombuster comparison.
The pattern is that this is an environmental failure with an environmental answer. Almost everything people try on it, retry loops included, costs more than the waiting would have.
Frequently Asked Questions
Sources & Further Reading
- Phantombuster documents this error in troubleshooting Error During Loading Of Chat Widget.
- The missing Send button case is separate, covered in how to fix the Missing Send Button or Premium Account Needed error.
- For follow-ups that never arrive, see how to fix LinkedIn follow-up messages not being sent.
- And the whole family of platform errors is collected in fix LinkedIn and Sales Navigator platform errors, worth a bookmark.
Related Articles
How to Fix Expandi Messages Not Sending (Pending Invites)
A connector campaign opens with a connection request, and a lead who already has one pending cannot receive a second. So the campaign has nothing it is allowed to do, and it says so in a tab most people never open.
Working Around the Limitations on Salesflow (2026 Guide)
CSV import exists, so does a campaign type for contacts you already hold, and so do shared blacklists. The constraints that actually bite are narrower: rejected Sales Navigator URLs, per-route caps, and a deliberate block on duplicates.
How to Fix Dripify Lead Collection Stalls (2026 Guide)
Most stalled collections have finished or are waiting. The Lead Collection Report names the cause, the search cap ends runs silently, and working hours suspend lead loading as well as sending.
How to Fix Expandi Data Sync and CSV Export Stalls (2026)
Three of the most common versions of a broken Expandi sync are documented behaviour: the export is emailed rather than downloaded, a known lead is deduplicated on purpose, and a field over 300 characters is dropped in silence.