Why Cant I Block Someone On Linkedin After Unblocking Them Exclusive __exclusive__ ❲720p❳

Why you can’t block someone on LinkedIn after unblocking them (and what to do about it)

Short version: LinkedIn intentionally prevents immediately re-blocking someone you just unblocked. This is by design to avoid accidental cycling between block/unblock and to keep user-management actions deliberate. Below is a clear, practical, and engaging guide explaining why this happens, what LinkedIn’s rules are, the consequences, and simple steps to resolve it.

Profile Access Required: To block someone, you typically must be able to visit their profile. If they have blocked you in return during the unblocked window, you may lose the ability to find them to initiate a re-block. Why you can’t block someone on LinkedIn after

Group Ownership Conflict: You cannot block a member of a LinkedIn Group if you are the Group Admin or owner. You must remove them from the group first. Conversely, you cannot block a Group Admin if you are a member; you must leave the group first. How to do it: Go to their profile

Review your "Public Profile" settings to hide specific sections from non-connections. Profile Access Required : To block someone, you

The One Exception (Premium Users Only)

If you have LinkedIn Premium Career or Recruiter, you can bypass the 48-hour wait by completely deleting your interaction history with that person (messages, connection requests, and profile views). Go to “Settings & Privacy” → “Data Privacy” → “Manage your off-LinkedIn data” → Request deletion of all activity with [Name]. This resets the relationship to “stranger” status, and the block button reappears in ~2 hours. This is an undocumented feature—LinkedIn support will never tell you about it.

6. The "Block to Unfollow" Hack

Many users block someone simply to force an unfollow, then unblock them immediately to keep them out of their feed without causing "drama." LinkedIn’s 48-hour rule specifically kills this hack.

If it still won’t work

Connection Loss: Unblocking does not restore a previous connection. If you want to be connected again after the 48-hour window, you must send a new connection request.