Thanks for your answer and your detailed explanation.
I suspect the reason you keep seeing the message is that you aren¡¯t clicking the OK button, or perhaps not exiting cleanly from TWS. So try doing a full logon and a tidy shutdown, and you should never see this message again (until IBKR announces another new API thing).
I¡¯m clicking on the OK button every day, I see it after every automatic restart. And any restart, stop/start that I might do
So here¡¯s a question: are you actually using TWS properly, ie fully logged in with your live or paper-trading account? If so, I really don¡¯t understand how you can be seeing this message, and you would need to take that up with IBKR.
Well, I would say that I¡¯m using it properly. Taking into account that is launched in a container and managed by IBC, but yes.
If you have been using it properly logged in, you¡¯ll probably have noticed that once login is complete, other dialogs are also displayed, such as the ¡®Welcome¡¯ dialog that is displayed to new users, and others that I noticed yesterday when running TWS 10.26 on a ¡®virgin¡¯ computer. IBC doesn¡¯t handle any of these, because they either only appear once, or a means is provided via the UI to prevent them being shown again; and also because IBKR keeps changing them! In general, IBC doesn¡¯t handle things that are easily dealt with once-and-for-all by the user, unless they are also shown by the Gateway: the Gateway is a different case, because it is likely that there will be no user present to deal with unexpected dialogs. For example there are commercial operations that use Docker images which contain Gateway ¡®as installed¡¯, ie exactly as Gateway is set up when first installed, with no user customisations: this is not really viable with TWS, because it is so much noisier, and I¡¯m not prepared to put in the programming time to handle that frequently-changing noise Another thing: I suggest that you set StoreSettingsOnServer=yes in your config.ini. This will ensure that your settings at the end of a TWS run are automatically uploaded to IBKR, and then reinstated when you run it again. Note that this only happens of TWS is closed tidily: if the IBC/TWS process is terminated (eg via a kill command), the settings are not uploaded. So any changes during that session are lost. You can also configure SaveTwsSettingsAt in config.ini to have your settings uploaded to IBKR on a specified schedule, though this is not really very useful.
I haven¡¯t set it on config.ini, but it¡¯s set on my config. This is actually working, because my layout and settings are identical to those I have on my PC installation.
I will try with SaveTwsSettingsAt
I just started TWS on my PC, and I don¡¯t see any message, back to the container and there it is. It¡¯s lost somewhere in between.
Alternatively you have to make sure that the TWS settings directory (which is /config/tws_settings according to your logfile) is on a Docker volume that will be persisted between runs: my knowledge of Docker is limited so I can¡¯t advise you on that. Also note that TWS only saves its settings at a tidy exit or on the SaveTwsSettingsAt schedule.
Yes, `/config` directory is persistent.
Thanks for your help. In any case this is just a small annoyance.
I¡¯m not sure there¡¯s a lot more I can say, but feel free to ask any further questions about this.
Richard
