[helene_t]

Web interface: This morning there was a tourney which was due to start in a few secs (and actually did start on time), as conrrectly indicated ("soon") in the first tap, but due to start in 14 minutes in the second tap.

I think it's because the web interface uses a refresh-as-needed method and isn't aware that the second tap needs refreshing.

[pescetom]

This sounds like a variant of the phenomenon I mentioned at the end of OP in my recent "two sessions" thread.
It seems that a web client can remain happily in limbo, responding to the user and convinced that it is connected to the server when in fact the server wrote it off several minutes ago.
As well as being a serious problem, this also contradicts the standard reply that there is a working bidirectional keep alive mechanism.

[pescetom]

Two days, no reply?
Seems like these problems only interest the customers.

[diana_eva]

pescetom, on 2025-May-24, 12:31, said:

Two days, no reply?
Seems like these problems only interest the customers.

Helene pointed out the issue and the reason. She was correct, the info does not auto-refresh, it only refreshes on reloading the tab. Other than yes, that's right, not sure what we could respond.

We'll improve this in an upgrade of the tourney list coming soon (comes with a full visual revamp, which won't have tabs at all).

[pescetom]

Fair enough, and sorry if I was impatient, but could you look at this my post https://www.bridgeba...36#entry1078336, too please?