This request has come as a result of the deletion issues experienced at APRA on the weekend.
Is it possible to implement a feature to abort a connector import / change detection run if an unexpected number of deletes are imported?
I'm thinking something along the lines of a flag to enable/disable, and a threshold value (either a number of entities, or percentage value).
Ideally this would be configurable per connector (as some may legitimately and regularly experience large changes in existing data).
This kind of issue has happened previously on other sites, and a feature like this could prevent temporary data issues within a source system from having impact on downstream systems.
Customer support service by UserEcho