Yes, I have to admit that when I saw routines with speaker notification ‘going local’ a while ago I did wonder how the speech was managed. I think I just trusted the tagging/messaging and put it down to magic!
I didn’t look at/notice other notification types a I knew these must rely on cloud by thier very nature. Kinda thought the speech may be encoded at time of creation and held locally… I guess, maybe ![]()
Only really look at these things as a general user these days - it works how it works and only really notice behaviour/changes when it impacts what I need. Tend to take everything else at face value.
Thanks @nayelyz , the behaviour actually makes a lot of sense in that notifications are lost but other actions are not. Previously all a routines actions would have been lost so this is a gain. Some clearer messaging for those like, in this instance, me (
) would be good.