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.

[Prasad Pagar · Accepted solution]

Hi,

Please change your flow properties to this and try

Hope this helps 🙂

Please mark my answer correct and helpful if applicable.

Thank you
Prasad

[Aditya24]

Hi Prasad,

It works fine. But can you help me understand the reason/logic behind this.

What is the difference between the two options and when to select what? How it impacts.

[Prasad Pagar]

See this sir

Setting Run As | ServiceNow Developers

Thank you
Prasad

[Prasad Pagar]

Basically 

• User who initiates session: The flow runs as the user who triggered the flow. For example, if a flow executes when a record is created, the flow runs as the user who created the record.
• System User: The flow runs as the System User. The System User is not a user record from the User table. System is a service account that is not restricted by access controls.

Thank you
Prasad