Weird behavior querying layer after deleting features with geoprocessing task

09-11-2015 09:07 AM
New Contributor

I have a custom geoprocessing task that deletes features from a layer. If I query the layer after the geoprocessing task finishes succesfully, I get the deleted features returned, but if I do the query a second time I get the correct results back (deleted features aren't returned). This occurs doing the queries programatically or directly on the REST Endpoint.

Any ideas of what can be causing that weird behavior?

Tags (1)
0 Kudos
0 Replies