Why RunAS is changing automatically to Who initiates the session in flow designer

[Haceena Shaik]

Hi all,

Greetings of the day!

We implemented flow designer for Group Creation, Adding Members, Removing members in AD.

As number of actions increased, we created subflows for each. In flow properties, we given run as to - System.

But Automatically, Subflows are changing  RunAS to Who initiates the session.

I'm unable find the way why its changing autmatically.

Please help me to reproduce this issue.

Regards,

Haseena

[AnveshKumar M]

Hi @Haceena Shaik ,

I have implemented similar kind of solution some time back and tested now in my PDI it is working fine and running as system user only. But if the sub-flow is configured to run as "User who initiated the session" it is not running as System user.

Is the sub flow is also configured to run as "system user" or the "user who initiated the session"? If the sub flows are configured to run "User who initiated the session" try changing it to "System" user and test.

[Haceena Shaik]

@AnveshKumar M . Thanks for the quick response.

 Yeah. I tried changing to System User and retriggered. Its Ok when I triggered. But why it's happening and what might be the reason for automatically updating to Who Initiates the session.

Regards,

Haseena

[AnveshKumar M]

@Haceena Shaik Sub flow properties won't change automatically. I suspect two things.

1. The Instances of flows which started before updating the run as user might be causing the issue for that particular instances
2. Please check sub-flows are successfully published after updating run as user to "System".

[Ankur Bawiskar]

@Haceena Shaik 

you need to manually update the Run as for subflows.