Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Release Lock does not work on service based request



In an IAC application, the motive is to acquire lock by making a service call and using the release lock activity. While passing the job id and the operator id in the request, requestors  are unable to unlock the work object.

Error Messages

No Error Message.

Steps to Reproduce

1. Create a service package which calls an activity.
2. Have the activity to call release lock method on a page created by opening the work object by using Obj-Open-By-Handle and using the work object key.
3. Call the service from the IAC application and check the behaviour

Root Cause

On doing a normal service call without authentication will not be able to acquire the lock as it will seem as if the request is not coming from the same operator id. For 'Release Lock' functionality to work, it must be ensured that the operator is the same.


Adding basic authentication to the service call resolves the issue.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us