I initially didn’t pay close attention to the details in this video. I created the .ps1 PowerShell file, converted it to an .exe file, and tested it by running the application directly. The .exe worked perfectly when clicked manually! However, when I tried to schedule the .exe with Task Scheduler, it failed to work. After following the steps in the video more closely, I found the solution: using Task Scheduler to directly execute the .ps1 file instead of the .exe file. The key was to set the "Action" field to "powershell -executionpolicy bypass -file C:\path\to\your\powershellscript.ps1". This allowed the script to run successfully.
Having trouble with this. Help would be very much appreciated. The ps1 file presses the keys however it does not trigger the flow only default action if any.
Thanks for sharing. However, it's not working. I follow the steps, and when running, only the Command prompt appears and disappears without any other action.
I tried this. It is working if I execute the powershell script but it is not working from Task Scheduler. I also tried to put the powershell logic in a batch file and trigger the batch file. Same issue. If I double click the batch file it is working but not working from task scheduler. Not giving any error also. The shortcut I am using is Ctrl + Alt + Q. Any help will be appreciated.
I have the same issue .. shortcut itself is working, manually executing the script in powershell is working but when task scheduler is executing the script it doesn't work. Did you find a solution?
Mine was also failing to work but then managed to fix it: Keys to start the flow: (Ctrl + Shift + P) #Powershell script: [void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") [System.Windows.Forms.SendKeys]::SendWait("^{+P}") Then on the task scheduler i had to put the full part for power shell, I had to first test in manually first in cmd to see it it work and it worked fine and started the flow. C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe Then on the argument: -executionpolicy bypass -file C:\path\to\your\powershellscript.ps1 The only change I'm now facing is that when the flow start they is a input variable pop up which appears which needs user intervention for the flow to start, how do i solve this.
I am not good with power shell but I added this code and it worked: $Timer = New-Object Timers.Timer $objectEventArgs = @{ InputObject = $Timer EventName = 'Elapsed' SourceIdentifier = 'Timer.Elapsed' } Register-ObjectEvent @objectEventArgs $Timer.Interval = 5000 $Timer.Autoreset = $False $Timer.Enabled = $True Wait-Event Timer.Elapsed [System.Windows.Forms.SendKeys]::SendWait("{ENTER}")
After so much research found this video and worked like a charm
Thank you for this video. It worked perfectly for me. I made sure that the shortcut key wasn't assigned to anything else beforehand.
Fantastic video. Thank you for this solution!
I initially didn’t pay close attention to the details in this video. I created the .ps1 PowerShell file, converted it to an .exe file, and tested it by running the application directly. The .exe worked perfectly when clicked manually! However, when I tried to schedule the .exe with Task Scheduler, it failed to work.
After following the steps in the video more closely, I found the solution: using Task Scheduler to directly execute the .ps1 file instead of the .exe file. The key was to set the "Action" field to "powershell -executionpolicy bypass -file C:\path\to\your\powershellscript.ps1". This allowed the script to run successfully.
Million thanks!!! This really worked for me.
its worked for me. Thank you AIP
After I save the file Program can't run, any same problem?
Having trouble with this. Help would be very much appreciated. The ps1 file presses the keys however it does not trigger the flow only default action if any.
it's working fine , many thanks.but a question? is this way working if I logout from the virtual machine??
Thanks for sharing. However, it's not working. I follow the steps, and when running, only the Command prompt appears and disappears without any other action.
me too, look like a sendkey is not work in physical
Which keys are you using? Can you try switching to a Function Key instead, like F6?
Same for me. Script is ok but task not :/
thank you for your video helps me alot but can you explain for me how can I get the file file.ps1 and which content that file.ps1 have? Thank you alot
I tried this. It is working if I execute the powershell script but it is not working from Task Scheduler. I also tried to put the powershell logic in a batch file and trigger the batch file. Same issue. If I double click the batch file it is working but not working from task scheduler. Not giving any error also. The shortcut I am using is Ctrl + Alt + Q. Any help will be appreciated.
I have the same issue .. shortcut itself is working, manually executing the script in powershell is working but when task scheduler is executing the script it doesn't work. Did you find a solution?
Am sending Ctrl + Shift + X, what is the command?
Mine was also failing to work but then managed to fix it:
Keys to start the flow:
(Ctrl + Shift + P)
#Powershell script:
[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
[System.Windows.Forms.SendKeys]::SendWait("^{+P}")
Then on the task scheduler i had to put the full part for power shell, I had to first test in manually first in cmd to see it it work and it worked fine and started the flow.
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
Then on the argument:
-executionpolicy bypass -file C:\path\to\your\powershellscript.ps1
The only change I'm now facing is that when the flow start they is a input variable pop up which appears which needs user intervention for the flow to start, how do i solve this.
You will have to pass the input variable automatically to prevent it.
I am not good with power shell but I added this code and it worked:
$Timer = New-Object Timers.Timer
$objectEventArgs = @{
InputObject = $Timer
EventName = 'Elapsed'
SourceIdentifier = 'Timer.Elapsed'
}
Register-ObjectEvent @objectEventArgs
$Timer.Interval = 5000
$Timer.Autoreset = $False
$Timer.Enabled = $True
Wait-Event Timer.Elapsed
[System.Windows.Forms.SendKeys]::SendWait("{ENTER}")
lets give it a try. nice hack :)
Is there any way when i open batch file it directly execute pda flow and if any system exception (user not logged)occurs write to text file or email..