Flow Designer Error – “The requested flow operation was prohibited by security rules” reoccurring

Hrithikah
Tera Expert

Hi Team,

I’m facing an issue in Flow Designer related to the error:
“The requested flow operation was prohibited by security rules.”

Background:

  • We have a requirement to create requests via inbound email, and this setup is currently working.
  • Earlier, when users with snc_internal role attempted to create requests through email, the flow failed with the same security error.

Initial Fix Implemented:
To resolve it, we made the following changes:

  • Set the flow to Run As: User who initiates the session
  • Added catalog_admin role in the “Run with roles” property of the flow (gave role to flow itself)

After this:
All users were able to successfully raise requests via email

Current Issue:

  • The same error has started occurring again:
    “The requested flow operation was prohibited by security rules”
  • The flow is now intermittently failing / breaking even with the above configuration in place
  • Create record actions are working, but update record actions are failing within the flow
  • Also, when System User is selected under Run As, the “Run with roles” option is not visible, limiting our ability to control execution roles
Any insights or suggestions would be greatly appreciated. If anyone has encountered a similar issue or has recommendations, please share.
6 REPLIES 6

Ankur Bawiskar
Tera Patron

@Hrithikah 

screenshots please

My thoughts

-> Mark Flow as Run as - System User

check this KB
Resolve flow failures caused by security rules for the system user 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Hrithikah
Tera Expert

 @Ankur Bawiskar , @Tanushree Maiti , @1__PrabakaranC 

Thank you all for your inputs.

I have added "Itil" role in the “Run with roles” property of the flow It is working but yes I will try changing the run ast to system user as well.

Thanks again for the suggestions.