Most eValid monitoring playbacks are launched from the scheduler. When the playback script is "desktop safe" -- it does not need access to the desktop to operate correctly -- then scheduler launched playbacks are very reliable.
However, when a script is not "desktop safe" -- meaning that somewhere in the script playback there will be a command that requires the use of a desktop window -- then this mode of scheduling may not work correctly in all cases.
eValid -B script.evs ...other command line options...
The EventLog will report that all the commands executed; this because eValid has no way of knowing that it's desktop oriented commands will be completed (it assumes they are). In eValid the desktop oriented commands are routed through the Windows operating system before being delivered to the eValid window, or to a desktop window that eValid is trying to control (e.g. through Desktop Recording mode).
Batch File Run-eValid.bat:The scheduler entry is one that invokes the Run-eValid.bat batch script:
Start eValid -B script.evs ...other command line options...
The scheduler calls RuneValid.bat as a separate process, which in turns calls the eValid executable, which then execute with will full privileges including access to the desktop.
Note: You might think that having the scheduler with "higher privileges" would make a difference here, but evidently it does not.
The eValid browser is launched, but without focus. After 100 msec a click is issued to the 150 x 150 location on the screen. This click, having been launched by a sub-process (not by the scheduler) will force focus on the eValid window in order to deliver the click.
SystemCall eVclick.exe 100 150 150
(Note: There should not be anything sensitive at the 150 x 150 location on the screen. If there is, use a different location on the browser face.)