Flow designer giving ACL error but in instance it is working fine.

[Aditya24]

I have a flow with:

Trigger: When Demand state changes to a custom state "Close Tasks".

Action: Set the state of the related demand tasks to "Closed Complete".

It is working fine for Admin but for other users it is showing error "The requested flow operation was prohibited by security rules".

ACL what I have on Demand task is that it can be edited (write ACL) if the state is not closed complete. 

User is able to make changes to demand task in form view and can set the state to closed complete and after that the demand task becomes non editable. Then why when doing through a flow it is giving ACL error for same user.

Please suggest.

[Aditya24]

A flow with an Action.

[Ankur Bawiskar]

Hi,

If you set the Run as User - System then the ACLs won't be evaluated as it is service account

more details below

Setting Run As

Regards
Ankur

[Aditya24]

Hi Ankur,

Understood.

So by doing this Run as System I am kind of giving an elevated privilege and bypassing all the ACL restrictions. It works fine but I don't understand why the Run as user who initiates is not working as the same user is able to do that in the environment on the demand task form. (As I have mentioned in my original question).

The same user can set the state of the demand task to close complete so that means the user pass the ACL criteria but then why the flow stops with ACL error?

Another question is, when to use which option, what is recommended by ServiceNow?

Please suggest.

[Ankur Bawiskar]

Hi,

in that case you might have to debug it further.

Regards
Ankur

[Appli]

Hi, I see it's marked as Accepted/Resolved but you may check if your flow contains subflows; settings for the Run as option in a flow don't apply to child subflows (= might be a reason why Run as user, who initiates, is not working as the same user is able to do that in the native environment).

Hope it helps