When working in Sandbox, it is sometimes necessary to remove accounts through aggregation, especially with setting up JDBC connectors where an errant query might pull in a large number of extras. If the excess value exceeds the 1-20% allowed by the UI, then the API will need to be used to update the accountDeleteThreshold.
In most cases, this changes is only needed for a short time, usually a single run to clean them up. It would be beneficial if the Source Aggregation endpoint has a parameter that was used just for that run. This would reduce the need to update the source with the new value, then update it back after correcting, thus reducing the possibility of disable.