Possible causes:
1- The flow connection was added after the Flow had added to the PowerApps causes new connection is not reference correctly in the PowerApps
2- User lacks of license to use the premium connection
3- User lacks Permission to read Flow in organization
{
"error": {
"code": "0x80048306",
"message": "
Principal with id a23ab0be-xxx-xxxx-xxx-0022xxx8989 does not have ReadAccess right(s) for record with id 443dd60d-xxx-xxxx-xxx-
1f5558f1288e of entity workflow. Details: {\"CallerPrincipal\":{\"PrincipalId\":\"a23ab0be-xxx-xxxx-xxx-0022xxx8989\",\"Type\":8,\"IsUserPrincipal\":true},\"OwnerPrincipal\":{\"PrincipalId\":\"80b19dc2-91f8-ea11-a815-002248168989\",\"Type\":8,\"IsUserPrincipal\":true},\"ObjectId\":\"443dd60d-ea02-407d-9269-1f5558f1288e\",\"ObjectTypeCode\":4703,\"EntityName\":\"workflow\",\"ObjectBusinessUnitId\":\"5365c433-cc8c-ea11-a811-000d3a851f9b\",\"RightsToCheck\":\"ReadAccess\",\"RoleAccessRights\":\"None\",\"PoaAccessRights\":\"None\",\"HsmAccessRights\":\"None\",\"GrantedAccessRights\":\"None\",\"Messages\":[\"PrincipalHasOwnerPrincipalWithAtLeastBasicPrivilegeDepth = False\",\"EntityUserGroupRights = None\",\"MinimumPrivilegeDepthRequired = Local\",\"SecLib::AccessCheckEx2 failed. Owner Data: roleCount=3,...<TRUNCATED>
Mitigation steps:
1- The flow connection was added after the Flow had added to the PowerApps causes new connection is not reference correctly in the PowerApps
=> Remove the affected flow in PowerApps datasource => Save => Publish => Edit app again => add Flow => Republish app.
2- User lacks of license to use the premium connection
=> Assign premium license for user to run the flow
3- User lacks Permission to read Flow in organization
Go to Advanced Settings
Check the Security that the user has, in this scenario, the affected user has Basic User. Check Customization tab, in Process entity grant Business Unit level for the Read access as below:
Good luck!
