Is it possible to control / increase the timeout in the Dispatch Console so it can stay open for longer before throwing up the "Salesforce session is invalid. Dispatch console will close now." notification?
This may help:
The Dispatch Console (DC) timeout value follows the same value set for your Org; this is enforced by Salesforce.
To check what that value is, click: Setup | Security Controls | Session Settings.
This is Salesforce functionality in relation to the session timeout. When the DC is inactive (not communicating with the Salesforce server) the connection is terminated. Salesforce does this so that users do not establish a constant link to their server and tie up server resources.
It's also possible that something in the background caused a logout. For the DC in particular, this could be as simple as closing the source Tab that you opened the DC link from (ex. if you close the Home Tab after launching/opening the DC from Home Tab link)..
Thanks for this. Our experience is that the console can close after only a few minutes (the timeout is set to two hours) so this suggests that it's to do with the closure of the source object. We're monitoring this, but if proved to be the cause, this presents a significant irritation. Our main dispatcher will often create an event from a Work Order and close it but needs the console open to monitor / plan other, unrelated WOs, but keeps getting kicked off. Any tips?
Hi Hugh - by any chance are your dispatchers working off of a very long list of work orders? We have experienced issues where one of our dispatchers had a default view that was trying to pull in 10x the work orders as another dispatcher (literally - 1000 work orders vs 10000 work orders) . I created a new dispatch console work order view (separated PM work orders by a few major accounts), which significantly reduced the amount of work orders the dispatchers were dealing with at one time. This definitely solved our issue. Maybe your situation is similar.