HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
For exactly the example you have given
When a user has deleted something and realised before replication occurs, it would be very simple to get it back from another replica
Additionally, the size of deletion stubs is not insignificant
The link you have given is unreliable and very slow, and freezes the client while the db is consistency checked
It also does not deal with design element deletion stubs
In what situation would you want to remove deletion stubs manually?
Applications, especially those that replicate between client and server or between servers need to maintain those deletion stubs in order to keep other replicas updated. Removing deletion stubs in one replica would just cause deletions to replicate back in from another database.
Please note that this method exists How to purge document deletion stubs immediately - IBM