Why can't I change Flow designer to run as System

[Frans Brus - No]

Why can't I change Flow designer to run as System?

I have this flow Run as User who initiates session but need to change this.

I checked documentation and I should be able to change it like in this screenshot:

But I don't have the option.... Also tried to Elevate Roles but that does not seem to work.

What do I do wrong?

[Frans Brus - No · Accepted solution]

Just found the cause: It is triggered form inbound Email....

In documentation >

NOTE: Flows with an Inbound Email trigger always run as the user who sent the email or the Guest user. The Run As value cannot be set for flows with an Inbound Email trigger.

The solution is to set Roles on the flow

[Michael Jones -]

How are you accessing the top record? It doesn't look like it is being loaded in Flow Designer. 

You might try opening it directly in Flow Designer and see if the behavior changes. You might also need to make sure you are in the Global application when you open it to make changes (I can't recall is scope matters for flow changes). 

Last, but not least, was this a flow developed in the instance stack where you are making the change, or was it brought over from an external source? I've occasionally seen issues where you're not able to modify a flow that wasn't started on your instance. You might try using Copy Flow and see if you're able to edit the copy, etc. 

I hope this helps!

If this was helpful, or correct, please be kind and mark the answer appropriately.

Michael Jones - Proud member of the GlideFast Consulting Team!

[Frans Brus - No · Accepted solution]

Just found the cause: It is triggered form inbound Email....

In documentation >

NOTE: Flows with an Inbound Email trigger always run as the user who sent the email or the Guest user. The Run As value cannot be set for flows with an Inbound Email trigger.

The solution is to set Roles on the flow

[Alex111]

Just wanted to report what we found out, this might be true in the past, but recently we created a FLOW, when asked we selected "run as" "system user", then added the inbound email trigger, this works fine.  BUT, if you start with "run as"  "user who initiates session" after adding the inbound trigger you can not change that, unless you are sneaky and figure out the table that stores the flows and change it from that table.  Which is what we did after we saw failures, as Guest did not have rights to create an event in our system (probably most).

BTW, the table is sys_hub_flow.

Not saying it's suppose to work this way, but it does, when creating the flow, make sure to select Run as "System User" and you should be fine processing the emails, at least we did for creating events.

There is a KB that talks about this limitation, but so far it's working fine using this method.

[art_jones · Accepted solution]

Post is a bit old but wanted to add something:

I ran into the same behavior that the OP mentioned and could not get the flow to run as System User, even though the flow was updated and showed it should run as System User (it was originally set as 'User who initiates session' then updated). This is a flow triggered by record creation (case).

My fix was to copy the flow and then deactivate the old version.  The new copy works as expected and runs as System User.