Question

pyCommitError when case is saved

Hi Team,

I am getting the pyCommitError when trying to save the case .Need to know the exact scenario when this error pops up.

I saw the existing post where it was said if lock was released , and trying to save the case , in that scenario this error comes.In that case lock lost issue occurs not the pycommiterror

Also i dont want to go for ob-refresh and lock . as need to know the exact scenario where this issue occurs.

Thanks,

Arshad

***Moderator Edit-Vidyaranjan: Updated Platform Capability***

Comments

Keep up to date on this post and subscribe to comments

Pega
September 30, 2019 - 6:18am

Hi Arshad,

Pycommit error comes when lock of work object is held by another user. or if the WO is not saved properly after being updated.

Refer to this link: https://community.pega.com/knowledgebase/articles/troubleshooting-pycommiterror-create-copy-save-or-import-circumstanced-rule

September 30, 2019 - 6:23am

Ideally, this would occur because the lock on work object is not held while you are trying to save the work object. Are you acquiring the lock somewhere during the process?

Check your customized activities, if any operation you are performing related to "Obj-"

Pega
September 30, 2019 - 7:33am

pyCommitError can also occur if there are any issues at DB end.

Please check this post -https://community1.pega.com/community/pega-product-support/question/pycommiterror-while-saving-workobject