Unfortunately, the client error you mentioned (LS_cause=new.timeout.5 .2.error) is not enough to figure out what is going on.
Indeed, the error means that the client was unable to create the session in the expected time and therefore tries again.
This scenario can be caused both by client-side problems such as poor network conditions, and server-side problems with severe delays on the server.
You should check the server log looking for messages like this "Current delay for tasks scheduled on thread pool SERVER is ... seconds".

About missing updates, still valid my previous reply, with a log configuration good for troubleshooting this kind of issue.

Regards,
Giuseppe