Re: TWS asks for 2FA every 24 hours even though "Auto restart" for one week enabled
|
The screenshot shows that the first task is being stopped at 03:36:57 because it reaches its timeout. That means that when the next schedule start arrives at 03:42:01, it is no longer running, so a new task is started and this will be a new launch of TWS, and hence a full login. ? There shouldn¡¯t be any time limits to the tasks. If you think about the normal case where the thing loads up on Sunday and keeps running (and auto-restarting daily) all week, that is all the one task (the task being the instance of the batch file, not the instance of TWS which of course is reloaded each day at restart). ? You don¡¯t need the task start time and the auto-restart time to be the same. It won¡¯t help if the task has a defined timeout. ? By the way, launcher.log is not really relevant, as it contains no information relevant to IBC. The IBC logfile is much more useful. ? ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Mark Dabrowski via groups.io
Sent: 31 January 2023 14:12
To: [email protected]
Subject: Re: [ibc] TWS asks for 2FA every 24 hours even though "Auto restart" for one week enabled? As seen in the attached scheduled task history, it's the culprit..? I guess I need to disable it and enable it at exactly 2:32am, my first trigger time?
Again, as per today's C:\Jts\launcher.log
it does the 2:30 restart as expected without 2FA:
2023-01-31 02:30:24.899 [GU] INFO? [JTS-Main] - ------------------------------- TWS RESTART --------------------------------
but then the scheduled task launches at 3:42am (when I must have originally enabled the scheduled task) asking for 2FA every day:
2023-01-31 03:42:06.828 [PF] INFO? [JTS-Main] - ------------------------------- TWS RESTART --------------------------------
|
