Yes, that time difference must be due to timezone. So the timezone of your computer is America/New_York, as shown in the Java properties listing. But perhaps you have set the timezone in the TWS login options to be UTC? If so, then the start of the ‘time gap’ is presumably when TWS switches your Java VM from America/New_York to UTC. I don’t see any reason why this should cause any problems, but it might be worth doing some runs with TWS and the operating system both running in the same timezone.

?

My conjecture yesterday that the ‘relogin required’ might be due to it being Saturday is almost certainly incorrect. My paper-trading system runs all the way through from Sunday evening until restarting at 12:00 the following Sunday, and I’ve never seen ‘relogin required’.

?

If this is continuing to happen, it would be very helpful if you could run TWS manually (ie without using IBC), and note exactly what happens (there won’t be a useful logfile when the ‘relogin required’ occurs). It should behave exactly the same way when the Re-Login button is clicked as it does when run in IBC (because clicking that same button is all that IBC does here). But then something different ought to happen to enable or cause the re-login to actually take place, and I need to know what this is and why it isn’t happening when running under IBC.

?

I said yesterday that I thought I knew what to do to fix this, but after looking at the code for some time I realise that’s not the case. If I’m unable to make any headway with this, I’ll just have to use a brute force cold restart. For the paper-trading system that wouldn’t be too bad, but for a live system it would be unpleasant because it would mean the user having to do the 2FA alert acknowledgement, which would be unexpected and probably at an inconvenient time.

?

Regarding your suggestion of limiting the number of retries, I think that will sit nicely with the cold restart suggestion above. There is in fact a known reason for the ‘relogin required’ dialog to be displayed, which is when login to the same account is attempted at another TWS: IBC does handle this properly, but it cannot tell the difference between this valid reason and whatever is causing yours. IBC’s handling is the same in both cases (ie click the Re-Login button), so if that leads to a Login failed, then IBC could do a cold restart.

?

I’ll try to get that done tomorrow (Tuessday).