2026.3.2 - "Log in again" button on "Logged out" dialog doesn't always work

Hello,

Thank you for the screenshot of the browser console.

Both errors come from the PowerShell Universal admin console, which runs on Blazor Server.

Logging off and clicking "Log in again" both reload the whole page.

While the old page closes, the browser can still send a click or a mouse movement for a menu or dialog that the server has just removed.

The server then replies with "There is no event handler associated with this event" or "There is no tracked object with id".

It does not run anything for these late events, and the next page starts with a fresh connection.

We tested the same steps on a clean PowerShell Universal 2026.3.2 installation, with several log off and "Log in again" cycles, and saw neither these errors nor any functional issue.

The "Logged out" prompt with the "Log in again" button appears after a period of inactivity, based on the SessionTimeout setting, which is 25 minutes by default.

More details are on the App Settings page:
https://docs.devolutions.net/powershell-universal/config/settings/

Could you confirm whether anything actually fails when these errors appear, such as a login that does not complete, a blank page, or a page you have to refresh manually?

If everything keeps working, you can safely ignore these console entries.

If something does fail, please send us the following:

A HAR file and a console capture of the same session, recorded with "Preserve log" enabled in the browser developer tools
The page you were on just before logging off
Whether PowerShell Universal runs behind a reverse proxy or a load balancer, and on how many nodes

Best regards,