Loading

Sharing lock occurs when managed package is inactive

Fecha de publicación: Aug 18, 2026
Descripción

When a managed package is no longer active, a System Admin can still make sharing changes, but sharing recalculations will fail — resulting in an unreleased sharing lock. This can also occur when any licenses associated with the managed package are disabled or expired.

For example, if your org previously used a managed package for territory-based sharing rules and that package's license later expires or is deactivated, any user attempting new sharing recalculations will hit this lock, since the user making the change no longer has access to the entity being recalculated.

Subsequent sharing changes will fail with the following error due to the lock:

"The sharing calculation you requested can't be processed right now, because it interferes with another operation already in progress. Please try again later."

Solución

This solution explains how to resolve a sharing lock caused by an inactive managed package or an expired/disabled license, and how to prevent it from recurring.

Resolve the Existing Lock

Contact Salesforce Support so the sharing lock can be verified and manually released — this lock does not clear on its own since it stems from a loss of access on the entity being recalculated.

Prevent the Lock from Recurring

Move the managed package and/or its associated licenses back into an active state, then re-submit your sharing changes. Once the package and licenses are active again, the sharing recalculation should complete normally.

FAQ: Why does this error appear even though I didn't touch the managed package?

The lock can persist from an earlier failed recalculation tied to the package, even if your current change is unrelated to it. Until the lock is released, any new sharing recalculation attempt will fail with the same error.

How do I know if a managed package or its license caused this?

Check Installed Packages and License Management in Setup for any package or license showing an inactive, disabled, or expired status — that's the most common trigger for this specific lock.

Número del artículo de conocimiento

001035937

 
Cargando
Salesforce Help | Article