Hi @Chandrakanth V,
When a flow runs as System User, it bypasses the triggering user’s session restrictions, but it does not override all ACLs or platform-enforced security. Tables like sys_user_grmember (user-group memberships) and HR data have strict protections that still apply, which is why you’re seeing the “unknown error.”
A couple of tips:
Check System Logs > All right after the error .You’ll usually see the ACL/security rule that blocked the action.
Test the same operation with a background script on sys_user_grmember. If it fails there too, it’s an ACL/security restriction, not Flow Designer itself.
If this action is required, you may need to adjust the ACLs or create a Script Include/Action with elevated role context, then call that from Flow.
So , Run as System User ≠ unrestricted access everywhere. Platform security still applies.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
