When closing an MR and deleting the branch, receive an email stating that MR can no longer be merged

Summary

During a workflow, I close an MR that is no longer acceptable followed by deleting the branch as it is no longer needed. I will later receive a notification via email:

Merge Request !168 can no longer be merged due to conflict.

This notification is not necessary.

Steps to reproduce

1. Create an MR with a change
2. Later close the MR
3. Delete the branch

I'm unsure if there was a conflict PRIOR to the closure and/or deletion of the branch

I'm also unsure if the notification is kicked off during the closure of the issue, or the deletion of the branch

What is the current bug behavior?

I receive an email notification.

What is the expected correct behavior?

I should not receive a notification.

Output of checks

ops.GitLab.com