Flow designer approvers called from decision table not triggering

[Shraddha17]

I have configured decision table having requestor's organization stored in combination with organization's approver. When I call this decision and pass input as Requested For (from Get catalog variable) the approval is not getting triggered. However, when a "Test" the flow from flow designer interface, the approval gets triggered. What am I missing ?

[Shraddha17]

However in logs, I could see below -

Note - The designated approver has been given approver_user role.

[Tejas Adhalrao]

hi @Shraddha17 ,

From your screenshots, the flow configuration looks generally correct. What I'd verify next is the value coming back from the Decision Table.The Ask For Approval action expects a valid User or Group. If your Decision Table is returning an Organization record or another reference type instead of sys_user or sys_user_group then its wont work..Open the Flow Execution Details and confirm the Decision Table returns the expected approver at runtime.

If everything above looks correct, could you share the Decision Table definition?That would help narrow down the root cause

If this solution helped, please mark it as the accepted solution. Thank you!

[Shraddha17]

[Suryansh Verma]

@Shraddha17 

The Decision Table input and result should both use the correct reference types. If the table maps an organisation to an approver, pass the Requested For user’s organisation, not the Requested For user itself, and configure the result as a reference to sys_user.

Add an If condition to ensure that the returned approver is not empty before calling Ask for Approval.

The flow also contains two sequential Ask for Approval actions on the same RITM. Leave the Approval Field blank on the first manager approval and configure the RITM Approval field only on the final functional approval. This prevents the first approval from marking the RITM Approved before the second approval is created and avoids sequential approval-state conflicts.

If it is helpful, please mark it as helpful and accept the correct solution by referring to this solution in the future, it will be helpful to them.

[Deepak Shaerma]

hi @Shraddha17 ,

Please remove the make a decision logic and save the flow, and reattach it again, i also faced the issue, byReapplying it was fixed for me. Please give this a try, 

If it is helpful, please mark it as helpful and accept the correct solution