How to Fix Waalaxy Not Switching LinkedIn Profiles (2026)
Mostly not a bug: the extension holds one LinkedIn session at a time by design, and a paid seat covers one account. One Chrome profile per account is the fix, and reinstalling the extension is the step you should try last.
You click to change LinkedIn account in Waalaxy, the page reloads, and you are still on the same profile. Try again, same result. If you run outreach for several clients or reps, this looks like the tool quietly refusing to do its job.
It is worth saying plainly, because most write-ups on this call it a bug: it mostly is not one. The Chrome extension holds one authenticated LinkedIn session at a time by design, and a paid seat covers one account. What looks like a failed switch is usually that limit meeting a browser still holding another account's cookies. Here is how to work with it rather than against it.
Why the switch does not take
Three things overlap here, and only one of them is a glitch. Separating them saves you from applying a destructive fix to a limitation that no fix will remove.
| Cause | Is it a bug? | What to do |
|---|---|---|
| One session per extension, by design | No, it is the architecture | One Chrome profile per LinkedIn account |
| A paid seat covers one account | No, it is the licence | Budget a seat per account you run |
| Cookies from a previous account still present | Partly, the browser is the problem | Clear LinkedIn cookies, log in as the target account |
| Extension holding cached session data | Yes, occasionally | Update the extension, reload LinkedIn in a fresh tab |
| Switched without logging out of LinkedIn first | No, the order matters | Log out of LinkedIn, then out of Waalaxy, then back in |
The order in that last row is the detail people skip. Switching accounts requires logging out and back in through both LinkedIn and Waalaxy. Changing only one of the two leaves the browser holding a session the extension does not expect, and the interface reloads onto whichever account the cookies still describe.
The setup that actually works
Stop switching and start separating. Four steps, done once, and the problem does not come back.
Create one Chrome profile per LinkedIn account
Use Chrome's own profile feature, one per account, named after the client or rep. Each profile keeps its own cookies, its own extensions and its own logged-in state, which is exactly the isolation the extension cannot provide on its own. This is the fix, and everything below is maintenance around it.
Install Waalaxy separately in each profile
Extensions are per profile, so install it in each one and connect it to that profile's LinkedIn account. Now switching client means switching Chrome profile from the avatar menu, which takes a second and cannot get the sessions confused.
Clear LinkedIn cookies in the profile that is stuck
If a profile is still loading the wrong account, remove cookies for linkedin.com in that profile only, then log in as the account it is meant to hold. Do not clear cookies across every profile: you would log yourself out of all your clients at once for a problem affecting one.
Use an incognito window for a one-off
For an occasional look at another account without setting up a whole profile, incognito gives you a clean cookie jar that disappears on close. It is not a place to run campaigns, but it is a good way to check something without disturbing your main session.
Habits that keep accounts separate
Once the profiles exist, four rules stop them bleeding into each other.
- One active LinkedIn account per browser profile. Never sign into a second account inside a profile that already runs one, even briefly, even to check something.
- Name the profiles after the account. A profile called Profile 3 is one you will eventually use for the wrong client. A profile called the client's name is not.
- Let the extension auto-update. Some switch failures genuinely are stale extension data, and an update fixes those without any of the destructive steps.
- Never share a browser profile between people. Two people signing into their own LinkedIn accounts in one profile produces exactly this symptom, and it is the version hardest to diagnose because neither person sees the other's session.
The theme is that the browser, not the tool, is where account identity lives. Treat a browser profile as belonging to one LinkedIn account and the whole class of problem disappears.
If the extension is also failing on imports, that is a related but separate failure. We covered it in how to fix a Waalaxy lead import stuck at 0 percent.
Multi-account without browser gymnastics
Step back and the cost is visible. Running five clients means five Chrome profiles, five extension installs, five sets of cookies to keep apart, and a mental note about which window is which before every action. That is real overhead, and it grows linearly with your client list.
ReactIn connects several LinkedIn accounts to one workspace, because the sending happens on our servers rather than inside your browser. There is no local session to keep separate, so there is nothing to switch between. Every account is available in the same interface at the same time.
That is also where sender rotation and the unified inbox come from. Activity can be distributed across accounts, and every conversation from every account lands in one place, which is not something a per-browser-profile model can express: each profile can only ever see its own.
The honest limits: ReactIn also prices per sender, so five client accounts means five senders, and no tool exempts an account from LinkedIn's own limits or security checks. What changes is the operational overhead, not the rules. If you run one LinkedIn account, none of this matters and Waalaxy's single-session model is not costing you anything.
For a feature-by-feature view of the two, see our ReactIn vs Waalaxy comparison.
Account identity lives in the browser, not in the tool. Give each LinkedIn account its own browser and the switch stops being something you have to perform.
Frequently Asked Questions
Sources & Further Reading
- Waalaxy's own troubleshooting path for extension problems is on its bug on Waalaxy page.
- Google documents how to separate sessions in Chrome's guide to sharing and profiles, which is the mechanism this whole fix rests on.
- LinkedIn's position on automated activity is set out in its user agreement, worth reading before scaling any multi-account setup.
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.
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.
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.