When you upload a CSV the DataPusher gets called to do its thing.
On #2234 we added a couple of calls to resource_patch on datastore_create and datastore_delete to set the datastore_active extra on the resource.
This is all very well but this update on the resource triggers again the DataPusher, which pings datastore_delete and datastore_create, which trigger...
Not sure how we can handle this on the notify extension point, as we only get the model object there.