I do not think HA have such a cache for actions.
Maybe if there is a cloud service involved then that could hold the action or if you use some kind of notification for the action, since HA use a Google service for notifications when not directly connected to HA.
But really strange the action got executed after I restarted my iPhone. It was in some queue for more than 30mins.
I have not customized anything using vanilla Nuki integration.
a really dumb joke came to mind but I’m not going to make it because this is definitely not funny. It is weird though, not something I would expect.
Are you able to reproduce it / is it happening more than once?
As said before, I very much doubt HA is caching the request. The only thing I can come up with is if it might be IOS behavior causing this: if you put an app in the background and open it later, IOS may close the app and try to return to where it was when you open it again. Could tht be when the command is sent?
If that is it, then the behavior should coincide with you opening the HA app when you get home.
It cannot be something wrong in the HA backend, because you weren’t connected to it when you pushed the button.
Could it be that you have an automation to unlock the door when you arrive home?
You phone might act like you just got home and then unlock the door for you.