Under investigation. The issue appears to be related to the handling of re-authentication tokens within the browser session after an idle timeout.
As the root cause is still being evaluated, the following workaround is available:
If the workaround does not resolve the issue, please collect a support bundle including Host Client logs and contact Broadcom Support. For more information, see Broadcom Support Portal.