Attestation not working ver 8.0

Question

Hi Experts, 
 Attestation for Custom target system was working good, suddenly it's stopped working. 
 When I attest a single object from manager, No DecissionRequired is not getting triggered and triggers the abort request. 
 
 Says no approver found. I have given recipient manager's approval and the manager is already assigned. 
 
 Any pointers. 
 Thanks, 
 Aad

Markus Weiss-Ehlers · Accepted Answer

It has nothing to do with the cache but with your bad decision to choose another decision rule that is not eligible with your attestation. I would go for the decision rule ED as the description states "Department manager for permission attestation" or for EM as the description states "Employee manager for permission attestation".

Markus Weiss-Ehlers · Answer

The system aborts the System entitlement attestation because it cannot determine an approver for one of your approval steps. So if something has changed, it might be your data in the database that will be used to determine the approver (no configuration change but a change of content data like role owners etc). 
 
My suggestion is, check your approval workflow and check if the condition to identify an approver is still satisfied for the attestation that fails.

Markus Weiss-Ehlers · Answer

The approval method DM is only able to find an approver if the attestation case is based on either the Person table or the PersonInDepartment table. To be specific AttestationCase.ObjectKeyBase has to point to objects from one of those two tables. In your case of a system entitlement attestation, this will never be the case. 
 I doubt that your workflow has ever produced viable results for that kind of attestation. 
 But let's assume it does, it might do because you had some people assigned to the application role Identity & Access Governance\Attestation\Chief approval team which is meant to avoid aborts due to an insufficient amount of approvers. This would explain your observation that you have nothing changed but it stopped working. Someone removed all members of that application role, and that's why your faulty approval policy is now unable to find any approvers.