For a long time now I have gotten seemingly unnecessary “Connection lost, editing paused” messages in the Fibery desktop app and web UI. In some cases this had a cause, like actual disconnection from wifi or whatever, but in other cases it seems to have happened just from the computer going idle or something. I can understand if maybe MacOS puts the Fibery app to sleep or something, but importantly this does not happen with literally any other web UI app, including Notion, and several others that do similar things to Fibery. Often times - though not always - Refresh and Force Refresh don’t fix it, especially recently.
I don’t see any other posts about it so perhaps it’s just me, but I’ve had this happen across multiple devices, OSs, browsers, etc. I haven’t reported it before now because I guess I figured it would have been addressed by now, somehow, but if anything it seems to have gotten worse recently. Fibery’s handling of “disconnects” seems to be behind the state of the art and I really hope it can be significantly improved because it interrupts my work frequently.
Oh and I should also say sometimes it just doesn’t allow Rich Text editing at all after some time away from the computer, but it also doesn’t have the clear “connection lost” message. Often in these cases I can even edit other Fields but not edit text in a Rich Text, inexplicably.
Man, I’m pretty disappointed to have zero response from the team on this by now. I guess maybe I should use Intercom, but I was hoping to see if someone else had this issue, hence posting to the forums. I also find Intercom kind of maddening because I use multiple Fibery tabs and once I open it, it seems to (or used to?) open on every. single. tab. Anyway would love an acknowledgement that this has been seen, at least.
I can assure you that we do read everything that comes through the community, but we can’t always respond to every thread.
We’ve previously improved the handling of similar issues when the live updates connection was terminated, but rich-text docs still need the same treatment. Totally agree this needs to be improved.
Thank you, it means a lot to know it’s a known issue! I was particularly confused by the fact that Rich Text seemed to handle this much worse than other Fields. It makes sense now. I hope it can be improved ASAP since you’ve already solved it elsewhere because Rich Text is a critical and common use and I run into this constantly. I was really surprised no one else reported it in fact. And good handling of this sort of thing will be critical for the Mobile App too, I imagine (although the tech for handling it there may be different, of course).