Community
Participate
Working Groups
If the communication to a peer takes longer, communicating through a proxy in example, the auto-refresh is triggered before the previous cycle has been completed and the query result displayed. It looks like that the timer is restarted at the time the refresh is initiated, instead of the point of time the refresh (including the result processing) is completed. Therefore, the UI never leaves the "Pending..." state.
In Workbench, the default refresh delay is 15 seconds. I think we should use the same default here. Nonetheless, the down counting of the delay needs to start after the previous refresh is fully finished.
*** This bug has been marked as a duplicate of bug 368321 ***