Approval in Flow designer is being skipped due to no valid approvers.

oluseyiasol
Tera Expert

I built a flow that has an approver.   The flow is triggered by Service Catalog.  On that specific catalog item,  there is a reference field that points to the sys_user table.    The user selected in the reference variable( Supervisor) is designated as the approver.   The flow works correctly in our Test environment, but skips the approval and goes straight to closed incomplete on the RITM.    I have verified that the accounts used in both environments mirror each other.  Can anyone advise on what other areas i should be looking at.   Not quite sure of my next move. This one has me baffled.  Should i delete the reference variable from the catalog item, and re-create it?

3 REPLIES 3

Hemanth M
Tera Sage

Hi @oluseyiasol ,

Please check these
1)Check the Supervisor record in Prod, check if its inactive or Locked out

2)Check flow context and check Ask for Approval step logs in Prod

HemanthM_0-1793295256226.png

 

Hope it helps!

 

Hi @oluseyiasol ,

 

If this response helped, please close the loop by accepting the solution or ask a follow-up question.

 

 

Sandesh Powar
Kilo Sage

Hi @oluseyiasol ,

I came across a ServiceNow KB article that describes a similar issue where the Ask for Approval action is skipped with the warning "Skipped due to no valid approvers."

Reference: KB3225201 – Flow Designer "Ask for Approval" action skips with warning "Skipped due to no valid appr...

According to the article, this issue can occur when:

  • The flow uses a Decision Table to determine the assignment group or approver.

  • The flow runs under the User who initiated session context.

  • The initiating user does not have read access to the sys_decision_multi_result table due to its ACL restrictions.

  • Consequently, the approval action cannot retrieve the assignment group and skips because no valid approver is found.

The KB suggests three possible resolutions:

  1. Run As – System User: Change the flow's execution context to System User in Flow Designer/Workflow Studio properties.

  2. Assign the decision_table_reader role: If the flow must run in the initiating user's context, grant the required role to the relevant users, subject to your organization's security policy.

  3. Run with roles: Keep the existing execution context and add decision_table_reader under the flow's Run with roles configuration.

Since your issue involves a Supervisor reference variable, first check whether your flow uses a Decision Table to resolve the approver. If it does, this KB may be directly relevant.

 

Hope this helps! If this resolves your issue, please mark the response as helpful and accept it as the solution.

Regards,
Sandesh Powar
ServiceNow Rising Star