Support Article
Assignment corrupts sporadically
SA-11318
Summary
Assignments are getting corrupted sporadically with exceptions.
Error Messages
Following are the exceptions:
- OBj-save failed at step 11 of activity logeventupdates
- Lock gone exception : Save , Delete , or commit has failed because lock is not held
Steps to Reproduce
1.Create a flow.
2.Create a flow action.
3. Submit the flow action.
4. Check the exceptions in the logs.
Root Cause
The root cause of this problem is a defect in the application code/rules. which is as follows:
Exception 1:
OBj-save failed at step 11 of activity logeventupdates
In one of the custom activity of post processing of a flowaction there is a commit step in place which causes the issue hence developer is informed to remove that step and instead replace it with obj-save with out checking the write now option.
Exception 2:
Lock gone exception : Save , Delete , or commit has failed because lock is not held
In the activity reassigneventbyhandle user is updating the steppage EventToReassign many times but there is no lock held on that page and in the 16th step developer is committing the changes without holding the lock.
Resolution
As part of the SR two exceptions are addressed
1) Exception :
OBj-save failed at step 11 of activity logeventupdates
Resolution :
Developer must remove the extra commit in their custom activity and check the scenario.
2) Exception :
Lock gone exception : Save , Delete , or commit has failed because lock is not held
Resolution :
Developer must get the lock on the page before commiting or submiting, developer is informed to re-look into their design.
Published August 31, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.