Happy Business Starts Here

Zuora Alumni

LOCK_COMPETITION

Guidance on handling LOCK_COMPETITION errors



If you found my answer helpful, please give me a kudo ↑
Help others find answers faster by accepting my post as a solution √

1 REPLY 1
Zuora Alumni

Re: LOCK_COMPETITION

This error occurs when multiple calls are attempting operations which require exclusive locks.

 

There are several recommned courses of action:

 

Analyze your system

 

Determine if other jobs, tasks, integrations are attempting operations requiring an exclusive lock on the object you encountered the error

 

This includes Zuora jobs like BillRuns, Payment Runs, etc.

 

Enhance Error Handling 

 

The guidance is to use retry logic that

 

  • initially aggresively retries the call
  • after N-number of attempts - falls into to an increasing wait betwen calls
  • finally fails after N-number of attempts

 

Increasing wait time

 

There is an edge case where multiple calls all execute at the same time.

 

Having static values for the increasing wait could lead to an unlikely case where the lock is continually hit.

 

Introducing a random variable to the sliding wait would would minimize the chances of this.

 

 

Problem Persists

 

If you have verified there are no conditions which would potentially attempt multiple operations, and have tried more robust API Client Retry logic, please contact Zuora Global Support

 

Before contacting support, please reference : How To Document API Issues for Zuora Support

 

 

Additional Reference

 

For more information please see : API Error Handling Best Practice and Guidance

 



If you found my answer helpful, please give me a kudo ↑
Help others find answers faster by accepting my post as a solution √