Workflow Studio - Run As not showing in the Flow Properties

Pascal Verdieu
Mega Sage

Has anyone encountered how to change the Run As of a flow once created in Workflow Studio?  It doesn't appear in the flow properties like it did in Flow Designer (one of the reasons I miss FD dearly...)

 

PascalVerdieu_1-1744718330672.png

 

1 ACCEPTED SOLUTION

Pascal Verdieu
Mega Sage

Found it!

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0821206 

 

Issue
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.

Cause
This is an expected out-of-box (OOB) behavior for inbound email type flow triggers.

View solution in original post

9 REPLIES 9

Thanks for the assist!

Ankur Bawiskar
Tera Patron
Tera Patron

@Pascal Verdieu 

it should show after creation as well.

Did you try to clear instance cache using cache.do and then logout and login again?

If my response helped please mark it correct and close the thread so that it benefits future readers.

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

Hi @Ankur Bawiskar, I have that in 2 different instances, but just in case, I did the cache.do and logged out, used another browser and still the same 😞

@Pascal Verdieu 

Strange.

Is that happening with some other admin as well in your instance?

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

Pascal Verdieu
Mega Sage

Found it!

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0821206 

 

Issue
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.

Cause
This is an expected out-of-box (OOB) behavior for inbound email type flow triggers.