Session Timeout



I created a dashboard (version 2.4 / licensed) which is running on an IIS. There are UDAuthorizationPolicies as well. Everything works fine and I’m happy so far but there is one thing that bugs me and I hope there is a simple solution to it. When I haven’t used the dashboard for like 20-30 minutes and I start using it without refreshing the page (e.g. pressing F5, reopen the dashboard) error messages pop up in the lower right corner. pretty much every functionality is build on an SQL queries or on WMI actions. I get messages like:

‘you cannot call a method on a null-valued expression’


‘method invocation failed because [System.DBNull] …’

but the dashboard still works even though I’m getting these messages. When I press F5 and do the same action again, everything works fine without getting these error messages.

So, is there a way to keep the session alive or is it possible to query the timeout and popup a Toast message in order to get people refreshing their page? Any help is appreciated.



make sure that the app pool dont idle out, it do this default after 20 min, so IIS will terminate the app pool.
see the idle timeout section:


thanks, I’m testing it right now. Will keep you updated about the result in about 30 minutes :slight_smile:


unfortunately it didn’t work. I’ve set the application ‘Idle Time-out (minutes)’ to zero, recycled the application pool, restarted the page and I still get error messages.

one of my pages is kind of a monitoring page and there are several buttons which start sql queries and show the result temporarily in a modal window.

I get the error message:

‘Cannot send data if the connection is not in the ‘Connected’ State’

one refresh, everything works as intended.


@adam Hey Adam, do you have an advice for me?


Hi @H4nYolo,

It looks like the websocket is disconnecting for some reason. Can you look in the developer tools for your browser for any weird errors? If you press F12 it should open those up.


Hi @adam

seems like you pointed me in the right direction.

this is what I get after a while using the company standard IE:

when I do the same with Firefox ESR I have no problems at all means I need to figure out what they changed by policy to make IE fail after like 20 minutes.