Simply wait exactly 48 hours from the moment you clicked "Unblock".
: The other person can potentially see your profile and updates again. Safety risks
Prevent the user from seeing that you visited their profile to check their status. Click your icon at the top of your homepage. Select Settings & Privacy . Click Visibility on the left menu. Select Profile viewing options . Choose Private mode to become completely anonymous. 2. Tighten Your Profile Visibility Simply wait exactly 48 hours from the moment
Without a time restriction, a user could unblock someone, browse their private updates, monitor their professional changes, and then quickly re-block them before detection. The 48-hour window forces a user's profile to remain entirely visible to the unblocked individual, removing the shield of anonymity and discouraging stalking behaviors.
It provides a window for both parties to potentially reconnect on better terms before the block can be reinstated. Other Potential Barriers to Blocking Click your icon at the top of your homepage
The reason you can't immediately re-block someone on LinkedIn is not a bug, but a deliberate feature designed to prevent impulsive back-and-forth. According to LinkedIn's official policies, after you unblock a member, you're required to wait before you can block that same member again. This cooldown period applies regardless of whether you're using the desktop website or the mobile app. During this time, the system essentially puts a temporary hold on the block function for that specific user, preventing any action until the timer runs out. It acts as a digital cooling-off period, giving both parties a chance to reassess the situation.
After exactly 48 hours from the moment you hit “unblock,” the block button becomes active again. Select Profile viewing options
I Can't re-block someone I recently un-blocked on Facebook messenger
I reached out to LinkedIn Premium support with this exact scenario. Their official response was generic:
Many users searching are actually victims of stale client-side state, not a server-side block.