DistributedLock.Azure - Locks not being released as of 7/1/2024

[wnbittle]

We've been using this library for a few years now with success. We recently ran into an issue with it on all of our function apps around 7/1/2024 timeframe.

The errors we're getting are:

The soft deleted blob was not found.
RequestId:b3710d9f-801e-002a-0f49-e7e276000000
Time:2024-08-05T15:06:33.1727180Z
Status: 404 (The soft deleted blob was not found.)
ErrorCode: SoftDeletedBlobNotFound
 
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id: b3710d9f-801e-002a-0f49-e7e276000000
x-ms-client-request-id: 583cc707-3348-4d8c-9002-c7e2250824c2
x-ms-version: 2020-02-10
x-ms-error-code: SoftDeletedBlobNotFound
Date: Mon, 05 Aug 2024 15:06:33 GMT
Content-Length: 228
Content-Type: application/xml

The behavior we're seeing (we created a new storage container to test) is as follows:

1. The function receives a message from a source system
2. The function obtains a lock on that message's unique id inside a using statement
3. The function successfully performs the critical section work
4. The using never exits
5. The next request for that same message id waits for the allotted time, but fails to acquire the lock

When we look at the storage account the file is gone (so it successfully cleaned up). Here's the code we're using (sorry for the screenshot).

The crazy thing is that I can't find any information on the error above (SoftDeletedBlobNotFound) either.

What am I missing?