We did send out a patch for Paratext 9.2 this week that has a few Paratext Live fixes in it - your description makes me think you are running into a bug that has been fixed.
This patch isn’t released to all users yet, so you can either wait until it gets released to everyone or you can try changing Paratext to get pre-release patches (typing ‘pre-release’ in the help search box will show you the menu item to change the release stage, search for ‘normal’ for the menu item to change it back).
The main problems we’ve seen so far with Paratext Live in 9.2 is that some communication errors occur in real life situations that we didn’t see in our testing. There was also a problem with getting the session lock in some cases.
The main reason for the change was performance problems in the way that Paratext Live was doing communication with the server - each user would send a message every second, even when they had no data to send - this was required to get any updates from the server. We now use a way of communicating so that users can receive updates without having to send a request and we believe this will allow us to handle a larger number of users in Paratext Live sessions.
Since we now have users select who will be the primary editor of the session, it’s best for any reports related to Paratext Live to be sent by the person who was the primary editor. The log will contain more complete information about what was happening during the session. This is because the primary editor actually processes all messages sent by users in the session.
Hopefully we’ll get past the initial errors in Paratext Live soon - thanks in advance for your patience.
John+Wickberg
Paratext Support