Helldivers 2 sells the fantasy of coordinated chaos, but nothing kills momentum faster than staring at a greyed-out friend request while your squad is already dropping. This isn’t just a random bug or bad RNG. Friend requests in Helldivers 2 sit at the intersection of platform ecosystems, crossplay logic, and Arrowhead’s own backend, and if one piece desyncs, the whole system collapses.
Before you start spamming invites or reinstalling the game, you need to understand how the social layer actually works. Once you see where the handshake fails, the fixes make a lot more sense and stop feeling like superstition.
Helldivers 2 Uses a Hybrid Friend System, Not Just Platform Lists
Helldivers 2 does not rely purely on Steam friends or PlayStation Network friends when crossplay is enabled. Instead, it layers an in-game social system on top of those platforms, using Arrowhead’s backend to bridge PC and PS5 players. That extra layer is powerful, but it also introduces more points of failure.
If both players are on the same platform with crossplay disabled, invites usually route cleanly through Steam or PSN. The moment crossplay is turned on, the game prioritizes its internal friend system, even if you already appear as friends on your platform. That’s why platform invites can fail silently while the game insists everything is “online.”
Arrowhead Accounts Are the Real Gatekeeper
Every Helldivers 2 player is effectively tied to an Arrowhead account, whether they realize it or not. This account handles crossplay identity, friend requests, and squad matchmaking across platforms. If that account isn’t syncing properly, friend requests either won’t send or won’t appear at all.
Common causes include logging in during peak server load, switching platforms recently, or launching the game before backend services fully initialize. When this happens, the game may show players as offline, missing, or permanently pending. From the player’s perspective, it looks broken, but under the hood the account handshake never completed.
Why Friend Requests Fail Even When Names Are Correct
Helldivers 2 friend requests are case-sensitive and ID-specific, especially across platforms. A Steam display name is not always the same as the Arrowhead ID the game expects. On PS5, this gets even messier if privacy settings restrict cross-platform discovery.
Even when you enter the correct name, the request can fail if one player’s social service hasn’t refreshed. This is why restarting the game or returning to the ship can suddenly make a “missing” request appear. The system isn’t polling continuously; it updates in chunks.
Crossplay Toggles Can Soft-Break the Social Menu
Toggling crossplay on or off mid-session is one of the most common ways to break friend requests. The game does not always rebuild your social state correctly after the toggle. You may still see crossplay icons, but the backend is treating you as mismatched.
The safest approach is to set crossplay, fully close the game, then relaunch before sending or accepting requests. This forces a clean reconnect to Arrowhead’s servers and refreshes your platform bindings. It’s not elegant, but it works far more consistently than hot-swapping settings.
Server Load and War Progression Directly Affect Social Features
Because Helldivers 2 is a live galactic war, social systems are not isolated from server stress. During major orders, defense events, or patches, backend resources prioritize matchmaking and mission tracking over friend services. Friend requests are often the first thing to lag or fail.
When this happens, requests may send but not display, or appear hours later. If multiple players are affected at the same time, it’s almost always a server-side issue, not user error. Knowing this saves you from wasting time troubleshooting something you can’t fix locally.
Why Joining via Mission Codes or Quickplay Sometimes Works Better
Mission join codes and mid-mission invites bypass parts of the friend system entirely. Instead of resolving full social links, the game only checks session validity and platform compatibility. That’s why players often manage to squad up this way even when friend requests are broken.
This isn’t a permanent solution, but it’s a reliable workaround when Arrowhead accounts aren’t syncing correctly. Once you’re in the same lobby, the game is more likely to register each player properly, which can even make future friend requests succeed without further fixes.
Common Symptoms Players Are Seeing (Requests Not Sending, Not Appearing, or Failing to Accept)
All of the backend quirks above show up in very specific, repeatable ways. If your squad can’t link up, chances are you’re hitting one of these patterns rather than doing anything wrong. Recognizing the symptom is half the fix.
Friend Requests Fail to Send or Instantly Error Out
This usually looks like the request button doing nothing, briefly spinning, or throwing a vague error before snapping back. In most cases, the game never actually submits the request to Arrowhead’s servers, especially during peak hours or right after a patch.
The fastest workaround is to back out to the ship, open the social menu again, and resend the request. If it still fails, fully close the game and relaunch before trying again. This forces a fresh handshake with both Arrowhead’s backend and your platform network.
Requests Are Sent but Never Appear for the Other Player
This is the most common and most confusing symptom. One player sees the request as sent, but the recipient never gets a notification or entry in their pending list.
This is almost always a sync delay between platform services and the in-game social layer. Having the receiving player return to the ship, open the social menu, or restart the game can trigger the request to suddenly appear. If it doesn’t show up after a full restart, the request likely never propagated and needs to be resent.
Friend Requests Appear but Can’t Be Accepted
Here, the request shows up correctly, but accepting it either does nothing or fails with no feedback. Sometimes it briefly accepts, then vanishes without adding the friend.
This usually points to a crossplay or account binding mismatch. Both players should confirm crossplay settings match, then restart the game before attempting acceptance again. Accepting from the ship rather than mid-mission also improves reliability, as fewer systems are competing for server updates.
Accepting the Request Works, But Friends Still Can’t Join Each Other
In this case, the social menu shows you as friends, but invites fail or lobbies appear unavailable. The game thinks the link exists, but session permissions never fully resolve.
Joining via mission code or Quickplay is the best temporary fix. Once you’re in the same lobby, the social state often stabilizes, and standard invites begin working again afterward.
Platform-Specific Issues on PlayStation, Steam, and Crossplay
PlayStation players often run into PSN syncing delays, while Steam users may see requests stall if Steam briefly drops connectivity. Cross-platform pairs are the most vulnerable, as they rely on Arrowhead’s account layer to bridge two different ecosystems.
If you’re playing crossplay, both players should verify they’re logged into the correct platform account, restart the game, and avoid toggling crossplay mid-session. This reduces the chance of creating a ghost state where both platforms think they’re connected, but the game does not.
Phantom States: Friends Missing, Duplicated, or Temporarily “Blocked”
Some players report friends disappearing from the list, showing up twice, or behaving as if blocked despite no block being set. These are classic signs of corrupted social cache data.
A full game restart usually clears it. If it persists, having both players remove and re-add each other after restarting can reset the relationship cleanly. It’s clunky, but it’s currently the most reliable way to clear phantom states without waiting on a server-side refresh.
Server-Side Causes: Backend Outages, Peak-Time Overload, and Matchmaking Desyncs
When all local fixes fail and friend requests still refuse to stick, the problem is often bigger than your console or PC. Helldivers 2 runs a live-service backend that handles social data, matchmaking, and crossplay handshakes separately from missions themselves. If any one of those layers hiccups, friend requests can fail silently or behave inconsistently.
This is where things get frustrating, because you can do everything right and still get blocked by server-side chaos.
Backend Outages and Partial Service Downtime
Arrowhead’s backend doesn’t always go fully offline when there’s an outage. Sometimes missions work fine, but social services like friend requests, invites, and lobby syncing are degraded. That’s why you might see requests send, accept, or disappear without ever completing.
The quickest check is Arrowhead’s official channels or community hubs to see if social services are flagged. If there’s a known issue, no amount of restarting or re-adding will fix it. Your best move is to wait it out or use mission codes as a stopgap until the backend stabilizes.
Peak-Time Overload and Request Queuing
During peak hours, especially after patches, warbond drops, or major events, Helldivers 2’s servers get hammered. Friend requests don’t always fail outright; they get queued, delayed, or overwritten when the server prioritizes matchmaking traffic.
If you’re trying to add friends during peak time, send one request, then wait at least a full minute before doing anything else. Spamming requests or canceling and resending can actually reset the queue and make things worse. If possible, try again during off-hours, when the social servers aren’t competing with thousands of simultaneous drops.
Matchmaking Desyncs Between Social and Session Servers
One of the most common hidden issues is a desync between the social server that tracks friendships and the matchmaking server that handles lobbies. The game may recognize you as friends, but matchmaking still treats you as strangers, which breaks invites and join attempts.
A reliable workaround is to fully exit to the title screen, then have both players re-enter at roughly the same time. From there, generate a mission code or use Quickplay to force a shared session. Once you’ve successfully loaded into the same ship, the servers often resync your social state in the background, restoring normal invite behavior afterward.
Cross-Platform Problems Explained (PS5 ↔ PC Friend Requests and Crossplay Bugs)
When friend requests fail specifically between PS5 and PC, you’re usually dealing with a different layer of problems than standard server hiccups. Crossplay in Helldivers 2 relies on multiple platform ecosystems talking to Arrowhead’s social backend at the same time, and that’s where things tend to break. Even if matchmaking works, the social handshake can fail silently, leaving players stuck in limbo.
Unlike same-platform issues, these bugs aren’t always fixed by restarting the game or resending a request. The problem is often how PlayStation Network, Steam, and Arrowhead’s own account systems sync identities across platforms. When one of those systems lags behind, friend requests don’t know where to land.
PSN and Steam Account Sync Conflicts
Helldivers 2 doesn’t use your PSN or Steam friends list directly for crossplay. Instead, it maps both platforms to an internal Arrowhead ID, and that mapping can desync after patches, crashes, or first-time logins. When that happens, requests can be sent but never properly attached to a player profile.
The most reliable fix is to force a clean resync. Both players should fully close the game, relaunch it, and remain on the main menu for 30 to 60 seconds before doing anything. This idle time allows the backend to refresh your account link instead of immediately jumping into matchmaking traffic.
Crossplay Toggle Mismatch and Ghost States
One of the most overlooked causes is mismatched crossplay settings. If one player has crossplay disabled, the game may still display friend options but fail to complete the request. Worse, the system sometimes caches the old setting, creating a ghost state where crossplay appears enabled but isn’t functionally active.
Both players should toggle crossplay off, back out to the title screen, then toggle it back on before restarting the game. This forces the client to re-register your crossplay status with the server. Skipping the restart often leaves the ghost state intact.
Friend Requests Sent to the Wrong Platform Layer
On PC, adding someone via Steam does not automatically make them available for crossplay invites. The same goes for PSN friends on PS5. Helldivers 2 requires an in-game friend request using the Helldivers friend code, not the platform-level list.
Always generate a fresh friend code and enter it manually instead of selecting a name from recent players. Old or cached codes can point to outdated session data, especially if either player has recently switched regions or network types. If the request doesn’t appear within a minute, cancel it and generate a new code instead of reusing the old one.
Cross-Region Matchmaking and NAT Type Interference
Cross-platform play is far more sensitive to NAT types than same-platform matchmaking. A strict or moderate NAT, especially on console, can block the return path of a friend request even if general matchmaking still works. This creates situations where Quickplay succeeds but direct invites always fail.
If one player is on PS5 and the other on PC, the PS5 player should check their network status and ensure NAT Type 2 or better. Enabling UPnP on the router or forwarding the recommended PlayStation ports can immediately fix request failures. On PC, disabling VPNs and network overlays can also stabilize the handshake.
Reliable Crossplay Workarounds When Requests Refuse to Work
When all else fails, bypass the friend system entirely. Have one player generate a mission code and share it manually. Joining via mission code forces both players into the same session server, often triggering a background social sync once you’re on the same ship.
After completing a mission together, return to the ship and try sending the friend request again. Many players report that once the game confirms repeated shared sessions, cross-platform friend requests suddenly start working as intended. This doesn’t fix the underlying bug, but it’s the most consistent way to squad up when the system fights back.
Platform Account & Privacy Issues (Steam, PlayStation Network, and Arrowhead Account Syncing)
If crossplay workarounds and NAT fixes didn’t move the needle, the next choke point is account-level syncing. Helldivers 2 sits on top of Steam, PSN, and Arrowhead’s own backend, and all three layers need to agree before a friend request actually resolves. When they don’t, the request can fail silently with no error message.
This is why friend requests sometimes vanish, appear delayed, or only work in one direction. The game may accept the input, but the backend never completes the handshake.
Arrowhead Account Sync Desyncs
Helldivers 2 relies on an Arrowhead account profile even if you never explicitly created one. If that profile fails to sync correctly, cross-platform friend requests will not register, no matter how clean your network setup is.
Log out of the game completely, restart it, and stay on the title screen for at least 30 seconds before entering the ship. This forces a fresh authentication handshake with Arrowhead’s servers. On PC, fully exit Steam first; on PS5, close the game from the dashboard instead of using Rest Mode.
If you recently changed your display name on Steam or PSN, this desync is even more likely. Name changes can take hours to propagate across Arrowhead’s backend, during which friend requests may fail outright.
Steam Privacy and Friend Visibility Conflicts
On PC, Steam privacy settings can block Helldivers 2 from resolving friend data correctly. Even if you can see your friends online in Steam, the game may not be able to query their profile.
Set your Steam Profile, Friends List, and Game Details to Public. Restart Steam after applying changes, not just the game. Several players report that friend requests immediately start working once Steam’s cached privacy data is refreshed.
Also avoid using Steam’s offline or invisible mode. Helldivers 2 treats invisible status as offline during crossplay lookups, which can cause friend codes to fail validation.
PlayStation Network Privacy and Crossplay Permissions
On PS5, PSN privacy settings are a common silent blocker. If your account restricts who can interact with you in games, Helldivers 2 may never receive incoming requests from PC players.
Navigate to PSN Privacy Settings and ensure “Who can interact with you through games” and “Who can send you friend requests” are set to Anyone. Also confirm that crossplay is enabled at the system level, not just inside Helldivers 2’s settings menu.
Parental controls, even on adult accounts, can override these options if they were previously enabled. Double-check that no legacy restrictions are active.
Cross-Platform Account Mismatch Edge Cases
One of the most frustrating bugs occurs when a player has multiple platform identities tied to the same Arrowhead profile. This can happen if you played early on PS5 and later switched to PC, or vice versa.
In these cases, the game may attempt to send friend requests to an outdated platform ID. The fastest workaround is to temporarily disable crossplay, restart the game, re-enable crossplay, then generate a brand-new friend code.
If the issue persists, both players should restart the game simultaneously and attempt the request within the same minute window. Timing matters more than it should, but synchronized logins reduce backend mismatches.
Server-Side Delays and Backend Outages
Finally, sometimes the problem isn’t on your end at all. During peak hours or after major patches, Arrowhead’s social services can lag behind matchmaking stability.
When this happens, friend requests may queue invisibly and only appear after a restart or long delay. If requests aren’t appearing after two minutes, cancel them, restart the game, and try again instead of spamming new codes.
Checking Arrowhead’s official social channels or community hubs can confirm whether social services are degraded. If they are, no amount of tweaking will fix it until the backend stabilizes.
Step-by-Step Fixes You Should Try First (Quick Solutions That Work for Most Players)
If you’ve already ruled out privacy settings, account mismatches, and known server outages, it’s time to run through the fixes that actually resolve the issue for most squads. These aren’t theoretical tweaks. They’re the same practical workarounds players use daily to brute-force Helldivers 2’s occasionally fragile social systems back into working order.
Fully Restart the Game (Not Just Back to Menu)
Helldivers 2 does a poor job refreshing its social layer after long play sessions. If you’ve been idling in orbit, swapping loadouts, or running multiple missions, the friend request service can silently desync.
Close the game completely and relaunch it. On console, make sure it’s fully closed from the system menu, not suspended. On PC, exit Steam entirely before restarting to force a clean backend handshake.
Regenerate and Re-Enter Friend Codes
Friend codes in Helldivers 2 aren’t static, and expired codes are a bigger problem than the game admits. A code that worked earlier in the session may fail minutes later without warning.
Have both players generate brand-new friend codes, then enter them manually instead of copy-pasting. Typos sound basic, but the game won’t always flag an invalid character, leading to a request that never actually sends.
Toggle Crossplay Off, Restart, Then Re-Enable
Crossplay is one of Helldivers 2’s biggest strengths and one of its most common failure points. The toggle doesn’t always apply cleanly mid-session, especially after a patch or hotfix.
Turn crossplay off, fully restart the game, then turn it back on once you’re in orbit. This forces the game to rebuild its matchmaking and social routing tables, which often clears stuck friend requests instantly.
Send Requests While Both Players Are in Orbit
The game’s social system behaves inconsistently when one player is mid-mission, browsing the War Table, or watching a cinematic. Requests sent during these states can fail silently.
For best results, have both players idle in orbit with no menus open. Send the request, wait up to 60 seconds, and only retry after a restart if nothing appears.
Join via Recent Players or Platform Friends List
If direct friend requests refuse to cooperate, use the side doors. Helldivers 2 sometimes allows squad joins through recent players even when the friend system is broken.
On PS5, try joining directly from the PSN friends list. On Steam, use the Friends menu to join game if the option appears. This can bypass the in-game request pipeline entirely.
Limit Rapid Retry Attempts
Spamming friend requests actually makes things worse. Each failed attempt can queue server-side calls that never resolve, effectively clogging your own request pipeline.
Send one request, wait at least two minutes, then restart the game before trying again. It’s slower, but it prevents backend desyncs that can lock you out for an entire session.
Check NAT Type and Network Stability
Strict NAT types and aggressive firewall settings can interfere with Helldivers 2’s peer discovery, especially in cross-platform squads. The game may matchmake fine but fail at social handshakes.
Ensure your NAT is Moderate or Open, UPnP is enabled, and no VPN is active. If you’re on Wi-Fi, a quick switch to wired Ethernet can resolve packet loss that only affects social features.
Sync Logins and Attempt at the Same Time
This sounds superstitious, but it works more often than it should. Helldivers 2’s backend occasionally struggles to reconcile player presence across platforms.
Have both players log in at the same time, wait until both are fully loaded into orbit, then immediately send the request. This reduces the chance of the system targeting an outdated session or ghost profile.
Advanced Workarounds to Squad Up Anyway (Join Codes, Mission Invites, and Social Menu Tricks)
When Helldivers 2’s friend system completely collapses, you’re not actually locked out of co-op. The game still exposes several lower-level squad entry points that bypass the broken request layer.
These methods aren’t obvious, and they feel more like speedrunner tech than intended UX, but they work because they hook directly into session matchmaking rather than the social graph.
Use Invite Codes to Bypass the Friend System Entirely
Invite codes are the most reliable workaround when crossplay or platform syncing is the root problem. Instead of relying on friend status, you’re directly telling the backend which lobby to target.
From orbit, open the Social menu, generate an invite code, and send it manually via Discord, PSN messages, or Steam chat. The joining player enters the code from their Social tab and connects straight to the session, even if neither account recognizes the other as a friend.
If the code fails the first time, regenerate it. Codes are tied to session state, so opening the War Table or starting matchmaking can invalidate an older one.
Leverage Mission Invites While Hosting Solo
Hosting a mission solo creates a more stable anchor point for invites. Helldivers 2 struggles most when both players are floating in orbit without an active mission context.
Select a mission, stay in the loadout screen, and then send a mission invite instead of a generic friend invite. This forces the backend to resolve a concrete session ID, which is harder for it to misroute or drop.
Cross-platform squads benefit the most here. PS5-to-PC connections, in particular, tend to succeed more often through mission invites than orbit-based joins.
Join Mid-Mission Through the Social Menu
The Social menu isn’t just for friends. If your friend is already deployed, their active mission can appear as joinable even when the friend request never went through.
Open Social, switch to Recent Players or Active Sessions, and look for their mission status. Joining mid-drop often succeeds because the game prioritizes filling active lobbies over maintaining social consistency.
You may load in slightly late or miss the initial drop pod sequence, but once you’re in, the squad remains stable for the rest of the operation.
Exploit Platform-Level Invites During Gameplay
Platform overlays operate outside Helldivers 2’s social stack, which makes them surprisingly effective. This is especially true when Arrowhead’s servers are under heavy load.
On PS5, use the PSN overlay to invite to game while the host is already in orbit or mid-mission. On Steam, right-click the player and use Join Game or Invite to Lobby if it appears, even if the in-game friend list is empty.
These invites hook into platform matchmaking APIs first, then hand off to the game, sidestepping the most fragile part of Helldivers 2’s backend.
Force a Squad Lock, Then Re-Invite
If all else fails, create a closed squad to stabilize the session before inviting. Set your lobby to Friends Only or Invite Only, start a mission, then back out to orbit without disbanding.
This refreshes the lobby instance without destroying the session ID. Once back in orbit, send invite codes or mission invites again. Players report significantly higher success rates after this soft reset.
It’s clunky, but it works because you’re refreshing the session without triggering a full social re-authentication, which is where most friend requests fail.
How to Check Server Status and Known Bugs Before Wasting Time Troubleshooting
Before you keep hammering invites or rebuilding squads, stop and verify whether Helldivers 2 is actually capable of handling social connections right now. A huge percentage of friend request failures aren’t user error or bad NAT types. They’re caused by backend issues that no amount of menu juggling will fix.
This is especially critical for cross-platform squads. PS5-to-PC friend requests are the first thing to break when Arrowhead’s services are under strain.
Check Arrowhead’s Live Server Status First
The fastest sanity check is Arrowhead’s official communication channels. When matchmaking, social features, or crossplay are degraded, they usually acknowledge it quickly.
Check the official Helldivers 2 Twitter/X account or the Arrowhead Game Studios Discord. Look specifically for mentions of “social services,” “friend requests,” “crossplay,” or “backend instability.” If any of those are flagged, stop troubleshooting locally and wait it out.
When servers are struggling, friend requests may send but never arrive, arrive hours late, or appear accepted while doing absolutely nothing. That’s not a bug you can fix client-side.
Understand Which Server Issues Break Friend Requests
Not all outages affect gameplay equally. Helldivers 2 can often let you quickplay or host missions even when its social layer is partially offline.
The friend system relies on account authentication, platform handshakes, and session routing all at once. If even one of those services is degraded, invites fail silently. That’s why you’ll sometimes see players online but unable to join them no matter what method you use.
If missions are loading but friends aren’t syncing, that’s a social backend issue, not a connection issue.
Watch for Active Crossplay and Platform Sync Bugs
Crossplay is one of Helldivers 2’s biggest strengths, but it’s also a recurring source of bugs. Arrowhead has repeatedly patched issues where PSN and Steam accounts fail to sync friend states correctly.
Common symptoms include friends showing offline when they aren’t, requests that vanish after being sent, or players appearing twice in the social menu. These are known bugs that come and go with updates and hotfixes.
If patch notes mention social fixes or crossplay adjustments, assume friend requests may be unstable for a day or two after deployment.
Use Community Reports to Spot Widespread Failures
When Arrowhead hasn’t posted yet, the community usually knows first. Reddit, Steam discussions, and Discord channels fill up fast when social features break.
If multiple players report identical issues within the same hour, it’s almost always server-side. That’s your signal to stop resetting routers or reinstalling the game. No amount of local troubleshooting beats waiting for a backend fix.
Treat community noise like an early warning system. If it’s loud, the problem isn’t you.
Decide When to Wait Versus When to Troubleshoot
If server status is green, no known bugs are active, and your platform services are online, then it’s worth trying the workarounds from earlier sections. That’s when mission invites, platform overlays, and squad locks actually shine.
But if social services are degraded, save your time and your sanity. Helldivers 2’s friend system either works or it doesn’t, and when it’s down, it’s down for everyone.
Knowing when not to troubleshoot is just as important as knowing how.
When Nothing Works: Reporting the Issue and What to Expect from Future Patches
When you’ve confirmed it’s not your setup and the servers are clearly the problem, the only move left is escalation. This is the point where player reports actually matter, especially for live-service games like Helldivers 2 that rely on real-world data to track failures. Arrowhead can’t fix what they can’t reproduce, and social bugs are notoriously slippery.
How to Report Friend Request Bugs the Right Way
If you’re going to report the issue, do it once and do it properly. Use Arrowhead’s official support site or the pinned bug-report channels on their Discord, not random social posts that get buried.
Include your platform, region, crossplay status, and exactly what happens when you send or receive a request. Screenshots of the social menu, error codes, or timestamps help far more than saying “friends don’t work.”
The more precise your report, the faster it gets grouped with similar cases. That’s how backend issues move from “known problem” to “hotfix priority.”
What to Expect After You Report It
Social features are almost always server-side fixes, not client patches. That means you won’t always see a download when things improve, and fixes can roll out silently.
If the issue is widespread, Arrowhead usually acknowledges it within a day on social channels. Actual fixes can take anywhere from a few hours to a full patch cycle, depending on whether the bug touches PSN, Steam, or their internal matchmaking services.
If it’s crossplay-related, expect delays. Any fix involving platform synchronization has to clear multiple approval pipelines, and that slows everything down.
Why Friend System Fixes Often Break Again
Helldivers 2 is constantly evolving, and every content update touches the same backend systems that power invites, squads, and matchmaking. Even a balance patch or new Warbond can accidentally destabilize social features.
That’s why friend request bugs tend to resurface after major updates. It’s not neglect, it’s the reality of a live-service game with cross-platform infrastructure.
The upside is that Arrowhead has consistently patched these issues once they’re identified. The downside is that stability often lags behind new content.
What You Can Do While Waiting for a Fix
If friend requests are dead, use temporary workarounds instead of forcing the system. Joining via recent players, mission invites, or platform-level invites often bypasses the broken layer entirely.
Stay logged in once you’re grouped. Logging out or swapping platforms mid-session increases the chance of desyncing again.
Most importantly, don’t burn yourself out troubleshooting something you can’t control. When social systems are down, patience is the real meta.
In the long run, Helldivers 2 remains one of the best co-op shooters on the market, even when its backend stumbles. Stick with it, keep an eye on patch notes, and remember: managed democracy is always better with a full squad.