QuestionQ31

Performance

Cloud Kicks, a global corporation, has this environment:

  • 50,000 users
  • A 24×7 call center operated by 25,000 users, including employees and contractors
  • A sales organization with 15,000 users

The sales organization began processing about 120,000 updates to Opportunity custom fields named priority and NextStep. It also began processing 20,000 updates to a highly nested territory hierarchy.

A third mass update was performed on a Next Step field on the Action Plan custom object, which has Case as a lookup field. Users began seeing a Group membership lock error in the system.

What is a probable cause of this error?

  • A Due to system-initiated sharing rule recalculation, there is Lock contention
  • B Due to Territory object updates, there is Lock contention on Territory object
  • C Due to Action Plan custom object updates, there is Lock contention on Case records
  • D Due to Opportunity object updates, there is Lock contention on Account records
Explanation

Salesforce uses an organization-wide Group membership lock for changes to a territory hierarchy. Concurrent processing while a large, deeply nested territory hierarchy is being updated can create lock contention and cause Group membership lock errors.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!