It prevents a behavior known as "block-hopping," where a user might unblock someone to view their recent activity or profile updates and then immediately re-block them to remain invisible.
before re-blocking the same member after you have unblocked them. This policy is designed to: Prevent Impulsive Actions:
Instantly deleting and restoring data connections across massive databases requires significant computing power. The delay reduces server strain caused by repetitive toggle actions. It prevents a behavior known as "block-hopping," where
of a group you are in. Similarly, if you are a group owner, you must remove the member from your group before you can block their individual profile. Shared Recruiter Accounts : If you share (or previously shared) a LinkedIn Recruiter account
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). The delay reduces server strain caused by repetitive
Change your settings so that only your connections can see your last name or profile photo. Alternative Solutions
I reached out to LinkedIn Premium support with this exact scenario. Their official response was generic: Shared Recruiter Accounts : If you share (or
When you block someone, your mutual connections, endorsements, and recommendations are permanently severed. The 48-hour window prevents users from accidentally triggering mass data deletion multiple times in a row. Other Reasons Your Block Option Might Be Missing
A: Go to Me > Settings & Privacy > Visibility > Blocking . Find the name and hit Unblock. There is no waiting period to unblock; the wait only applies to re-blocking.
If they converted their profile to a LinkedIn Page (unlikely but possible), you cannot block a Page—only unfollow it.
If instant re-blocking were allowed, bad actors could unblock a target, send an abusive direct message or leave a hostile comment, and immediately hide behind a block again. This would leave the victim completely unable to report the user or view the source profile to gather evidence. 3. Reducing Server Overhead