"Disconnected" simply means that the last operation couldn't reach the server. We don't really maintain much state beyond that.
F5 or clicking the folder always triggers a sync, and if that is successful it will clear the "Disconnected" message you see in the lower left corner.
Closing and reopening Kube should definitely not be necessary.

Just to make sure I understand correctly:

1. You opened Kube and some operation failed so you ended up in the "Disconnected" state (as signified by the status bar in the lower left corner).
2. You tried clicking the folder and pressing F5 but that did not result in any UI changes.
3. After a restart clicking the folder again triggered a sync as usual

If that is the case I'll have to try and reproduce it.

If you can reproduce it the log output from step 2 would be useful, clicking the folder or pressing F5 should result in at least some debug output. Also try waiting for 40s to see whether an open connection times out.

Unlikely to be flatpak specific.

In T6899#108593, @cmollekopf wrote:

"Disconnected" simply means that the last operation couldn't reach the server. We don't really maintain much state beyond that.
F5 or clicking the folder always triggers a sync, and if that is successful it will clear the "Disconnected" message you see in the lower left corner.
Closing and reopening Kube should definitely not be necessary.

Just to make sure I understand correctly:

1. You opened Kube and some operation failed so you ended up in the "Disconnected" state (as signified by the status bar in the lower left corner).
2. You tried clicking the folder and pressing F5 but that did not result in any UI changes.
3. After a restart clicking the folder again triggered a sync as usual
   
   If that is the case I'll have to try and reproduce it.
   
   If you can reproduce it the log output from step 2 would be useful, clicking the folder or pressing F5 should result in at least some debug output. Also try waiting for 40s to see whether an open connection times out.

You understand correctly , I will try to reproduce and give you some logs later today.

I can't reproduce that by disconnecting my internet:

• Tried an initial sink -> works
• Disconnected the internet and synced again -> results in disconnected state and error message after 40s timeout
• Connected the internet again and synced again -> works and clears the disconnected state

After reinstalling Kube, It seems that I had a PEBCAK moment.

Looking at the logs more carefully I have noticed that there was a disconnec, and now I can see the popup of connection lost (I somehow manged to miss that popup) .

Should we close this until we find any further evidence then?

Yes.