Approvals Fail to Lock data if Primary Members include children

Summary:

The Approvals fail at 'Lock' action after data is 'Approved'. This seems to happen when the children/descendants/base entities are selected as the Primary Members within the Approval Unit.

Content (required):

Hi,

We have encountered an issue when the Approvals fail at 'Lock' action after data is 'Approved' either by users or Admin. This seems to happen when the children/descendants or base entities are selected as the Primary Members within the Approval Unit. When the parent is selected as the only Primary Member then it works fine and the 'Lock' is successful.

The error message it gave did not include any insight or useful information (screenshot below).