Question3Replies1038Views×Close popoverChandana Teegala (ChandanaT3026) Accenture Accenture IN View ProfileSend Message ChandanaT3026 Member since 2017 1 post Accenture Posted: January 31, 2018Last activity: February 5, 2018Posted: 31 Jan 2018 4:27 ESTLast activity: 5 Feb 2018 3:39 EST Closed pyCommitError - Attempting to access a rule with a bad-defined on classI am getting this error "pyCommitError" Attempting to access a rule with a bad-defined on class while creating a case.Can anyone please tell what might be the issue?***Updated by moderator: Lochan to add Categories*** Case Management System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoPosted: 31 Jan 2018 5:37 EST×Close popoverCarissa Wenhardt (CarissaW_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. US View ProfileSend MessageCarissaW_GCS PEGA replied to ChandanaT3026What do you see in the trace? Posted: 3 years agoPosted: 5 Feb 2018 3:06 EST×Close popoverChandana Teegala (ChandanaT3026) Accenture Accenture IN View ProfileSend MessageChandanaT3026 Accenture replied to CarissaW_GCSIn the tracer I saw that Call Work_CommitWithErrorHandling step is failing. Is it related to cache issue or any other issue? Posted: 3 years agoPosted: 5 Feb 2018 3:39 EST×Close popoverMahendra Kumar Mahaveer Chand (Mahendra_Kumar) Verizon Verizon IN View ProfileSend MessageMahendra_Kumar Verizon replied to ChandanaT3026Hi, One of the reason for this error to occur is when pega tries to access a rule but the rule's applies to class is not moved. May be a newly created property xyz in class a-b was moved. But the class a-b is not present or moved in the environment.