>>That seems to imply an exception being thrown somewhere in $scope.getPagedDataAsync()? Do you have 'Pause on exceptions' checked in the debugger ?
>>IIRC correctly this method is no longer actually async - is that correct ?
>>
>
>Yes, this method does very little now - it just sends data to another method.
>
>
>>Also, can you explain how your logic regarding ' $scope.isEditLoading ' - why are you waiting 250ms before setting it true ?
>>
>>
>
>This is an interesting question - the code in the controller is auto-generated (we then add more logic). Why it is set this way I am not sure myself.
>
>Also, yesterday I commented out the paging options and enablePaging and still the behavior was the same. So, the problem is not in the paging, the problem is that when my data change, somehow grid doesn't react and display them. Only by switching to dev tools I can get it to react to that new data set.

In an MVVM situation which from my reading is what Angular Js is all about, for a control to update, it has to be notified that the underlying binding has been changed. In Silverlight/wpf that is handled by INotifyPropertyChanged and all works great. I'm sure there is a similar mechanism in Angular which you are not calling after mucking around with sort, etc.