Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.6.0
-
Untriaged
-
Unknown
Description
Perry noticed that cancelling queries wasn't working properly in 4.6 - the query continued to run on the server even though it was cancelled in the UI.
With some debugging I found that the problem was due to the cancel query specifying 'ClientContextID' instead of 'clientContextID', so the fix involves only changing a single character.