Delete a custom record under its relationship rules
What It Does
Permanent removal follows every relationship policy inside one transaction. Custom dependants are removed first, and any refusing member stops the complete deletion.
The Flow
When Something Fails
Keep a refusal in the dialog and explain restricting connections. The record remains until deletion commits. Raise a conflict identifying restricting types and roll back the deleting transaction. All prior link changes in that transaction are undone. A missed nudge waits for a later successful dispatcher schedule. Permanent file copies remain indefinitely under the absent cleanup binding.
Open Design Questions
File cleanup and the unused external deletion-check integration remain recorded gaps.