Maciej Zasadzki ADVICOS Report post Posted 10/22/2025 08:02 AM Hi, We are experiencing recurring issues with running our own external applications (written in Python and compiled to .exe) from the Run Program module. In the logs, everything seems correct and the path is valid: 092757.586 1585 5 1 785 state [add_initialPrompt2Library] Run Program | 092757.586 1585 5 1 785 rv replace start [C:\Aplikacje\promptsLibrary\addPrompt2Library.exe /s:"$RV[tts_save_filename_last]" /t:"$RV[dialogflow_init_responseMessage]"] 092757.592 1585 5 1 785 rv replace end [C:\Aplikacje\promptsLibrary\addPrompt2Library.exe /s:"C:\Program Files (x86)\VoiceGuide\temp\tts_5_2.wav" /t:"Witam. Jestem automatyczną asystentką firmy ABC."] 092757.593 1585 5 1 785 modrun file.exists [C:\Aplikacje\promptsLibrary\addPrompt2Library.exe] as supplied 092757.593 1585 5 1 785 modrun starttask_mode=cmdexe 092757.593 1585 5 1 785 StartProcessTask run:[C:\Aplikacje\promptsLibrary\addPrompt2Library.exe] args:[/s:"C:\Program Files (x86)\VoiceGuide\temp\tts_5_2.wav" /t:"Witam. Jestem automatyczną asystentką firmy ABC."] pref_mode=cmdexe bHideWindow=True 092757.593 1585 5 1 785 process_start_cmd_readoutput begin 092757.611 1585 5 1 785 StartProcessTask preferred process start method - net_noshell : started ok. dwProcessId=4224, hProcess=53288, dwThreadId=16964, hThread=0 092757.612 1585 5 1 785 find_next_vgm module=[asrDataCheck] (trigger={SUCCESS}) 092757.612 1585 5 1 785 modrun taking success path Despite this, the application does not seem to execute or perform its task. When we run the exact same command in a CMD window, everything works fine and the program behaves as expected. What conditions or requirements must be met to ensure external applications are properly executed from the Run module? Thanks in advance for any insights or troubleshooting tips! Share this post Link to post
SupportTeam Report post Posted 10/23/2025 12:12 AM Please try changing the 'mode' in which this .EXE is ran from the Run Program module. Suggest trying "simple" or "logged_in_user" from https://www.voiceguide.com/vghelp/source/html/modrunprogram.htm : Quote Task Start Modes VoiceGuide can start the program as a Simple Process, or run it as a Logged In User, or use the Shell to run it. The default option is set in VG.INI, section [moduleRunProgram], entry: StartTask_Mode Mode preference can also set during the call by setting this Result Variable: $RV[ini_moduleRunProgram_StartTask_Mode] Allowed settings are: simple logged_in_user shell cmd Share this post Link to post