Why Cant I Block Someone On Linkedin After Unblocking Them Exclusive -

If the person deleted their LinkedIn profile between the time you unblocked them and tried to re-block, the system cannot find a target profile to block. You’ll see an error: “Profile no longer exists.”

If you are worried about them viewing your profile during the 48-hour window, you can temporarily hide your public profile.

LinkedIn is not Instagram or Twitter. It is a professional graph database. Every block, unblock, and connection is a logged relational event. When you unblock someone, LinkedIn re-enables backend processes:

Re-blocking immediately would create conflicting states in LinkedIn’s graph database, potentially causing errors like ghost notifications or partial profile visibility.

Even after the backend cooldown expires, you may still not see the block button. Why? Because the LinkedIn mobile app and web interface cache your relationship status aggressively.

When you unblock someone, the frontend (what you see in your browser or app) keeps a local cache saying: “This user is unblocked as of [timestamp].” It does not automatically refresh the availability of the block action. You may need to: If the person deleted their LinkedIn profile between

Many users searching "why cant i block someone on linkedin after unblocking them exclusive" are actually victims of stale client-side state, not a server-side block.


LinkedIn stores your interaction history with another user as a state machine with these primary states:

When you unblock someone, you move from State 4 → State 5. In State 5, LinkedIn’s backend is busy:

Until this process completes, the system cannot allow a transition back to State 4 (Blocked). Attempting to do so would create a race condition, potentially leaving the relationship in an undefined state (e.g., half-blocked, searchable but not messageable).

From a database engineering perspective: You cannot apply a new block mutation while the previous unblock mutation is still propagating to LinkedIn’s read replicas. Many users searching "why cant i block someone


Immediately after you unblock someone, LinkedIn enters a 72-hour "cooldown" or synchronization limbo. During this period, the system is actively reversing the original block (restoring old connection data, messages, and engagement metrics). To prevent system conflicts and malicious "block-churning" (repeatedly blocking/unblocking to harass), LinkedIn’s API temporarily hides the block button for that specific user. You cannot block the same person again until the system fully reconciles your relationship history.

In short: You can block them again, but not right away. The wait time is typically 48 to 72 hours.


Under the hood, LinkedIn’s backend isn't just flipping a simple is_blocked = true/false switch. When you block someone, LinkedIn does something far more aggressive than other platforms.

To truly protect your privacy, LinkedIn often performs a relationship severance. When you block someone:

When you unblock them, the system must perform a complex rebuild of possible connections. It has to check: perhaps out of professional necessity

If you were allowed to re-block immediately, the database would enter a race condition—where the system is still cleaning up the first unblock while processing a second block. This leads to ghost profiles, half-deleted comments, and the dreaded "Something went wrong" error. The 48-hour cooldown gives LinkedIn’s distributed servers time to fully reconcile your relationship graph.

You made a decision. Perhaps it was out of anger, perhaps out of professional necessity, or maybe just an experiment. You blocked a connection on LinkedIn. Then, a wave of anxiety hit you. Did I just burn a bridge? What if they see I blocked them? What if they were a potential client?

So, you unblocked them.

Now, you feel a different kind of anxiety. The notifications are flooding back. Their posts are reappearing in your feed. That nagging feeling of “Why did I block them in the first place?” returns. You rush to their profile to hit the block button again.

Error. “You cannot block this user at this time.”

You try again. Nothing. You refresh the page. You try the mobile app. Same result.

Welcome to LinkedIn’s 48-hour unblocking cooldown. To the frustrated user, this feels like a bug. To a systems designer, it is a deliberate, intelligent, and (arguably) necessary feature. Here is the exclusive, deep-dive reason why you cannot block someone immediately after unblocking them.