Role Assignment Fails in Subflow Despite running with Admin/Scoped Admin Access — "Attempted to add blacklisted role: sn_hr_core.admin"Issue When a parent flow calls a subflow, and that subflow performs an action such as adding a user to a group, the action fails — even though the subflow is running with a scoped admin role (such as an HR admin role) that should permit it. Symptoms A parent flow calls a subflow.The subflow is intended to run with a scoped admin role (e.g., HR admin) that has permission to perform higher-security actions such as group membership changes.Within the subflow, an action like adding a user to a group fails.The following error is seen in the subflow's execution: Attempted to add blacklisted role: <role_name>The same action succeeds when performed directly in a flow that is not called as a subflow.The issue occurs specifically when this logic runs inside a subflow invoked by a parent flow — it does not occur when the same action runs in a standalone, parent flow. Release Australia Cause PRB2090999 - allowHighSecurityRoles never read for a subflow's own execution when invoked as a nested "Start Flow" instruction from a parent flow — blocks legitimately-allowed scoped-admin roles Resolution Move the subflow logic into the parent flow: Instead of calling a subflow to perform the action (e.g., adding a user to a group), rebuild that logic directly within the parent flow. Since this issue only affects actions running inside a subflow, doing the work directly in the parent flow avoids the problem. Related Links PRB2090999 - allowHighSecurityRoles never read for a subflow's own execution when invoked as a nested "Start Flow" instruction from a parent flow — blocks legitimately-allowed scoped-admin roles