How would that work for being able to view history of other people’s tasks?
Broadcast the change to all clients?
And if your client isn’t online to receive the broadcast? But later you need to research an error that happened earlier?
It’s still going into the database, and you still need to download the list initially. But just once when connecting. I’m not saying remove the manual refresh. But polling the server every 30 seconds from every client is not the right way to do this…
@timshuwy We are going around in circles here.
This is the response I got when I originally reported the problem (Case CS0005322374).
Now I’m being told to submit another support case to review the same problem again?
Wait… I’ve seen this skit before!
Constantly building tools to get around deficiency is getting more and more annoying.. I am sure we have not seen the last of this problem.
Edit note to self don’t post on Epiusers after another day of frustration.. Sorry just working as designed…
If we didn’t do that, Epiusers would be a very quiet place.
Tell them to improve MRP Performance by another 50% and stop dinking around with System Monitor. I can find a dozen of processes that are slow, Multi-Company, Global Scheduling etc… Took a guy who is not even on the dev team to fix MRP after a decade of slowness 
ok, It seems we are all getting wound up about a true bug, and not an “Idea”.. i dug deep into this and found that the idea has been linked to Jira ticket KNTC-29756 which has now been completed as of the end of april. no need to vote on the idea. it was a bug.
I was just looking in “Current Code” (bug fixed here) and the refresh button does a rest call, and retrieves the data and displays it.
I think that this subject can be closed now.