I talked with the Team about it, and we try different ways to simulate what is happening and for sure try to find a solution for it. So the Refresh when opening the Gantt View was something we introduce for Customers that has the same work in multiple Work List due to some specific business need. That is not what we recommend but that is something they can do. And with the current technologic we have available the refresh is required once the Data Model was not designed for a partial refresh, once that causes performance and inconsistent issues over data we already faced in the past. The option we advise to be used in those scenarios where the same work Order is used in different Records of Graphical Assignment and Graphical Scheduling is:
Field: Refresh When Opening Gantt View Table.
Indicates if the schedule or worklist will be refreshed every time the Gantt view is opened. If this check box is selected, the queries used to gather the schedule data will be run every time the Gantt view is opened, and new or updated work record data will appear. If this check box is cleared, data will only be refreshed upon clicking the Refresh Schedule button in the Gantt view
So that will need to be the change on the setup of the Work List to avoid this issue, and we will be able to have a Tech Note with more technical advice on what corrupts the current data model causing the load to fail once an inconsistency of records is found.
As part of current this explanation, that is something we will avoid in the next version of the Dispatching Dashboard once we will use a new way to handle that situation as part of the new Framework. Thanks and more than welcome to clarify if necessary.