We're using one LN Job running using planned tasks of Windows on our LN 10.2.1 system. The job is deleting the print history. LN will show a history of the job and the last time, the job was running in the job session.
So let's assume your job is not running in LN. Well obviously its planned task is started in Windows, but somehow it is "not going through" to LN. Your're basically executing a batch. In this batch there's bw.exe, which is used to start the Job in LN. Bw.exe may not be able to run the job, but it terminates without any windows error, so the planned task will show an errorless execution of the batch file.
I've been going through this too, when I was setting up the job: Windows executed the task, but no sign of execution in LN.
I tested the batch by manually executing it in remote desktop on the server. So you can catch basic configuration errors (i.e. bw.exe not found; missing access rights).
Then I started the planned task manually on the remote desktop. So you may get errors with the used windows user linked to the planned task. (Also check the windows error list of the server.)
I had to fix access rights and file path until it worked. Did you try executing your batch manually?
I did not use the Batch provided by Infor, I just started bw.exe like this:
[/rem Job in LN starten
"C:\Program Files (x86)\Infor\BW\ERPLN\bin\bw.exe" D:\erp61\job\job000.bwc
job00.bwc has to be configured for auto login.
In the field Command I've given the required parameter:
-set BSH_JOB=WARTUNG ttaad5203m000
In your case the field has to be empty, I think, because the parameters are added to the line of bw.exe. There's no need to change your batch. I'm just giving this as an alternative way.