Thank you very much for your help, this will make fixing the bug much easier for me.
The refresh one is a bit more complicated with the watch. Our forecast data is downloaded on the backend and the watch manages it itself ( when they have the resources, iPhone has good connectivity, time of day, etc). So it's hard to predict their refresh. When the data is downloaded, the backgroud thread will ask the system to refresh complications.
From my observation, the watch refreshes all complications in the morning ( the system has a prediction of when the user gets up ) so that when you put on the watch you have actual information. Then the refresh depends on what watchface you are currently using and gives priority to that.
I'm not sure if I'll push this through to the next release as it's already ready in the testing phase, but I'll look at it today and do my best.
Thanks again for your time and I'll let you know when it's fixed.