Question about run as current user

Content Authoring
1

Can someone confirm this? I believe this is correct.
The first execution command line after a runas=currentuser runs as current user, but the next execution command line runs as system?
for example; execution1.exe runs as current user, but execution2.exe runs as system.

override wait
runas=currentuser
completion=job
hidden=true
wait execution1.exe
wait execution2.exe

2

Can confirm.

Just ran the following as a test, and it behaved as described/expected (i.e. the override wait and it’s configuration applies only to the next wait command):

action uses wow64 redirection false 

override wait
	runas=currentuser
	completion=job
wait {pathname of system folder & "\notepad.exe"}

wait {pathname of system folder & "\notepad.exe"}

The first instance of notepad is opened up as the current user (and visible since I did not set hidden=true in my test). Once it is closed (since it is a ‘wait’ command), the second instance of notepad is opened up as SYSTEM (and not visible to the local user…killed it via Task Manager to end the action).

3

thank you that is what I thought would happen.
thank you for confirming this.