Lifetime management of time delayed message notifier?

[DoctorAutomatic]

I'm away from a computer (just boarded a plane) and was going to do some project planning/diagramming on paper. So I have no way to get this answer for a number of hours. I was curious if the delivery notifier reference for time delayed messages is managed internally (in the framework) or if we need to explicitly destroy the reference once we're done with it. My guess is it's managed internally but would appreciate knowing for sure.

[BertMcMahan]

Short version: The notifier is released by the framework.

Explanation: When you call "Time delayed send message" it async launches "Time-delayed send message core" which handles the time delays, any repeat calls, and receiving the notifiers from the caller. When it's done (either due to sending all of the requested copies, or getting some form of "stop it" message, or throwing an error, it will release the notifier.  If you manually destroy the notifier, it will also halt the time delayed sending of messages immediately.

Here's a pic of the code for reference since you said you didn't have your dev machine:

Edit:  I just saw the date on your post, guess you found your answer. Or maybe your airplane ride is REALLY long 🙂

PS... apparently, the word for "airplane ride" that starts with an F and rhymes with "write" is not allowed on this forum?