Flow Designer "Ask for Approval" action skips with warning "Skipped due to no valid approvers" when reading Decision Table output for non-admin usersIssue When a Decision Table is executed within a Flow Designer flow to evaluate and output an assignment group, the Decision Table completes successfully and evaluates the correct logic. However, when the flow is triggered by a non-admin end user, the subsequent Ask for Approval action fails to read the Assignment Group from the decision result table (sys_decision_multi_result). As a result, the approval step is skipped, and the flow execution log records the warning: Skipped due to no valid approvers. Symptoms 1. The Decision Table step (Make a decision) completes without error and evaluates the expected criteria. 2. Submitting a Service Catalog item or Order Guide as an administrator generates group approvals as expected. 3. Submitting the same request as a non-admin end user causes the Ask for Approval action to evaluate to skipped with the warning: Skipped due to no valid approvers. 4. In Flow Designer execution details, the configuration runtime value for the approval rule evaluates to empty (ApprovesRejectsAnyG[]), indicating that the assignment group field value could not be resolved from sys_decision_multi_result at runtime. 5. Access Analyzer logs confirm that read access to sys_decision_multi_result is Blocked for the submitting non-admin user. Release Applicable across all supported releases using Decision Builder and flow designer Cause The decision engine successfully determines and returns the output record to the flow. However, out-of-the-box (OOB) Access Control Lists (ACLs) on the Decision Table Multiple Result table (sys_decision_multi_result) grant read access only to users who have the decision_table_reader or decision_table_admin role.If the Flow is configured to run under the user session context (Run As: User who initiated session), the Ask for Approval action attempts to read the Assignment Group field from sys_decision_multi_result using the initiating non-admin user's security context. Because the end user lacks the decision_table_reader or decision_table_admin role, platform security blocks read access to the result record, causing the Assignment Group data pill to return null and skipping the approval action.ACL on sys_decision_multi_result table: https://<instance_name>.service-now.com/now/nav/ui/classic/params/target/sys_security_acl.do%3Fsys_id%3D02f66afd5393301097a3ddeeff7b1236 Resolution Option 1: Change Flow Execution Context to "System User" To allow Flow Designer to read the decision result fields without requiring end users to have administrative/reader roles on platform decision tables: Open Workflow Studio (or Flow Designer) and open the impacted Flow. Click Properties (top-right controls). Locate the Run As setting and change it from "User who initiated session" to "System User". Click Save and Publish. Note: Executing the flow under System User context grants elevated system privileges during execution, allowing the Ask for Approval action to successfully extract the Assignment Group from sys_decision_multi_result regardless of who initiated the session. Option 2: Assign decision_table_reader Role to Initiating End Users If organizational policy strictly mandates that the flow must execute under the initiating user session context: Navigate to User Administration > Roles.Assign the OOB decision_table_reader role to the impacted end users.Verify that non-admin users can now read the sys_decision_multi_result record fields, allowing the approval action to retrieve the assignment group. Option 3: Even if the flows' 'Run as' is set to 'User who initiates session', add 'decision_table_reader' role in 'Run with roles' section.