Flow designer "run as" property not updating correctly for inbound email type triggered flowsIssue When updating the property "run as" to system user in the flow designer properties, flows still execute as the user who initiates the session. Changing the property and saving or activating again does not change this property. When using the built-in test flow functionality, the flow correctly runs as system, but in test mode, the flow runs as the user.CauseThis is an expected out-of-box (OOB) behavior for inbound email type flow triggers.ResolutionInbound Email triggered flows run as the User who sent the email (or guest if the email sender cannot be resolved to a sys_user record).See the below documentation.Flow Designer trigger types With other types of flows, you can choose to run as a system user or the user who initiates the session. However, inbound email flows always run as the sender of the inbound email. If the system does not recognize the sender, inbound email flows will run as the Guest user. The actions of inbound email flows are limited by user Access Control List (ACL) restrictions. To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow. If there is a need to perform work in the flow that requires privileges the sending user may not have, that work must be moved to a subflow with "Run as System." A "Run As System" subflow within a Run As User Flow will Run As System.