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]

Understood. So by doing this I am kind of giving an elevated privilage 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 on form 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?

[Prasad Pagar]

Its definitely ACL blocking sir.

Please debug your ACL's and also check Flow Statistics and Logs for clear understanding on how its executed and where its failing.

Thank you
Prasad

[RC12]

hi. the flow has been saved and activated. can u tell me where to go and find the flow properties settings. i cant a make a new one.. i have to make changes in this one actually. plz help

[Prasad Pagar]

Hi,

Click on this

and then

Hope this helps

Thank you
Prasad

[Pranesh072]

are you using client callable flow, subflow, or action?