Bruce, I'm assuming "cancel delay actions" should work on both an action with a delay and a standalone delay actions? I'm seeing an error in logs related to delayed actions in rules where I'm using a standalone delay actions and cancel delay actions in the same rule.
I don't have a screenshot of the error at this time, but will upload it next time I see it. Stop actions this rule seems to work without the error, but it some cases it's not an acceptable workaround since it cancels more than just specific actions with the "delay cancel" flag.
The notify google commands are for google assistant, the one that runs after my the door is closed triggers my "nest x yale lock" to lock.
The IF master bath door closed then notify is another google assistant command that triggers a lighting flash (via a google assistant to yonomi action) in my master bathroom if the door is closed as the occupant might not hear the announcement in the shower.
The logging is a snippet of "past logs" centered around the time of the error, perhaps the last entry was a result of new trigger after the rule has already run. Since the rule is tied to the front door it does get a lot of activity throughout the day.
OK. So turn on all of the rule logging, so we can tell what's going on. As it is, there's no way to tell. Those logs are very confusing, and don't line up at all with the rule you've shown. So until then, it is impossible to even begin to tell what is causing the error. Also, need to capture the entire log sequence of the rule being triggered until it throws the error.