Hi All, Our mirrored HealthShare environment has failed over a few times recently due to underlying infrastructure issues (that are being worked on and resolved). In the HealthShare logs we are seeing: 10/06/22-00:54:35:925 (4736) 1 Journal Daemon has been inactive with I/O pending for 10 seconds: gjrnoff=524741316,iocomplete=523852600,filecnt=1011,fail=0 10/06/22-00:54:55:086 (4736) 3 CP: Pausing users because Journal Daemon has not shown     signs of activity for 30 seconds. Users will resume if Journal Daemon is active again My question is: 1. While the issue is being resolved, is there anywhere I can increase the time HealthShare will wait for the Journal Daemon to become active? We are seeing it come back after around 40 seconds, so 10 seconds to late to prevent the failover. 2. If so, are then advisories or considerations for upping the limit to say 45 seconds? Many thanks