Fix recipient handling in create_notification method

[dorkdiaries9]

Summary

Adds a defensive check in create_notification() to skip processing when recipients is provided but empty.

Details

• Prevents unnecessary calls to _process_recipients()
• Adds debug log for traceability

Testing

Validated that:

• Notifications continue working normally for valid recipient lists
• Debug log appears and processing stops for empty lists

Type of Change

• Bugfix (non-breaking change)

[Maffooch]

Please base your changes against the dev or bugfix branch

[valentijnscholten]

@dorkdiaries9 Thanks for the PR. Does it fix an actual bug or is it more defensive/optimization. I haven't looked at the code, but I wonder where this notification for 0 recipients is triggered.

[dorkdiaries9]

Thanks for the PR. Does it fix an actual bug or is it more defensive/optimization. I haven't looked at the code, but I wonder where this notification for 0 recipients is triggered.

Thanks for reviewing!
This change prevents unnecessary notification processing when the recipients list is empty.
Earlier, the method continued execution even if recipients was an empty list, which could lead to redundant logs or unintended calls to _process_recipients.
So, this is a small bug fix to ensure that we only proceed when there are valid recipients.

[mtesauro]

Approved