any idea what could be causing this?
Usually exceptions cause this problem - a server-side exception is thrown when you open the page and the application crashes as a result.
Check your application's logs for any tips. The exception could also be logged in the browser's developer tools.
it's after the page is just sitting there and it does it on all pages in my app.
it's a timeout issue I think, something is closing the web socket?
with azure app service web sockets on and always on on, I would think the page would stay open 'forever' like a 'normal' web page?
I think this is how Blazor server works. The socket is closed after inactivity: ASP.NET Core Blazor SignalR guidance | Microsoft Learn
I don't know the specifics of azure app service. This however seems as a generic Blazor nuance unrelated to Radzen.
1 Like