maxAllowableOffset in the REST API is returning wrong responses when called consecutively milliseconds apart

08-14-2015 11:16 AM
New Contributor II

Hi all,

We are using the query operation on a MapService with the maxAllowableOffset. There are multiple queries made and they are happen really fast. Chrome tells me that they are 1ms apart. In this case, response is wrong. Sometimes we get the same geometry back, sometimes we get the previous operation's geometry back etc. When we introduce a 50ms delay between the ajax calls in javascript, the responses are correct. This looks like a bug due to some global state shared across requests. This thread from 3.5 years ago also seems to be indicating something similar. IdentifyTask, QueryTask and MaxAllowableOffset - after setting it does not get reset

Thank You,


Tags (2)
0 Kudos
0 Replies