Improved Logic for Smart Lock "Code Not Sent"

A Smart Lock Code Not Sent message recently triggered twice for two different edge cases. Would love to see the logic updated to accommodate. Relevant user feedback on the completed feature, too: https://feedback.hospitable.com/p/backup-codes-hospitable-code-communication. Some ideas on how to do it:

1) If users edit a message already populated by %smartlock_code%, or send it early, that should not break the flag that the code was sent. Depending how it’s implemented, perhaps a new message status "SentEarly" instead of “Cancelled,” or a simple recalc and regex check. Recent example: I customized a message, but didn’t touch the %smartlock_code%-generated code, the message was treated as manual, and the Code Not Sent message triggered.

2) If a message with %smartlock_code% is in the queue, send that instead of the generic Code Not Sent message. Recent example: Check-in time 3pm. Guest booked same-day at 8pm and the “new reservation” message triggered. Code Not Sent message was sent 8:16p (10 minute delay), then the queued message scheduled for “3 days before check-in” triggered at 8:29pm (22 minute delay). Could be fixed other ways e.g. shorter delay on overdue messages, or message logic allowing “new reservation made after check-in.”