Flow Designer Run as set to 'System' but firing as user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2024 06:48 AM - edited 03-12-2024 07:01 AM
Hi,
I have the following error when executing a flow "The requested flow operation was prohibited by security rules.". Reading similar posts it appears i need to run as 'System User' rather than "User who initiates session" in the Flow Properties. See screenshot.
However when i run this flow i can see that the 'Run as' is still set to the user?!?!? I have obviously saved and activated the flow numerous times but i dont know what is going on... any advise/help would be appreciated. thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2024 02:51 PM
Hi,
I could not see the screenshot. Maybe you will need to attach it again.
The changes would take effect only for next executions after you alter this property, save it and Activate the flow again. Maybe is some old version execution that was still running.
Otherwise, if this is still happening, I would suggest you to create a new flow mirroring the steps (you can simplify it for testing 1st attempt) to check if there was an issue when updating the Run As field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2024 09:31 AM
When a flow is run "as system", but has approvals, I have noticed that actions after the approval executed as that approver. When the approver has the right roles, all is good. If the approver does not have sufficient roles to perform the actions (i.e. creating a catalog task), that message can be thrown.
What I have done to get around this is to move the restricted actions like creating tasks into a subflow where you can set the subflow to run as the system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2025 05:01 PM
I need to create a conflict record, the ACL is only allow create where role has admin. So I created a subflow with "run as system user" in our test environment and it worked. So trying to do the right thing, I also applied the fix to the development environment and then promoted back up to test and I cannot get it to work...period. If I run the subflow by itself using the test button and feeding in the change number, the subflow creates the record OK, but if I try to run the subflow from a flow which is not run as system user, the record is not created. I tried turning debugging on and I can't see any ACL resolutions from the flows. Just another reason to hate flows in my book.
