August Lock reporting state change, but not actually changing (aka locking)

So this is a new one, and I haven’t had a single issue with my August Lock Pro (3rd gen) and hass since the day I installed it. But over the past couple days, I’m noticing my front door is unlocked for hours upon end. This is strange since i have a few automations to always keep the door locked when I’m away, or even at home — even redundant entity state checks to lock it if its been unlocked for too long.

I have one specific automation when i walk my dog to lock the door 1 minute after i leave. I came back from that walk tonight and the door was open still. I checked node red and hass dev states and they both said the “lock state” was initiated and completed; but its not locked?

Ive confirmed the batteries are at 95%, connect bridge is in the same spot its always been and is fully connected to hass and the lock, august app locks and unlocks the door (although with a significant delay prior to before. Maybe 20 sec?). But what gets me is the state in hass/node red says its locked when it isn’t and never even attempted too. This seems like a failure in the communication between the hass intergration and the august connect bridge.

Anyone else seeing this type of behavior lately? Maybe an August API change?