Have you checked out #d1-open-alpha ? That might be exactly what you're looking for
Have you checked out #d1-open-alpha ? That might be exactly what you're looking for
await in your ctx.waitUntilwaitUntil takes a Promise and by using await, I'd assume you're actually waiting for the Promise to complete for .put before the result is passed to waitUntilwaitUntil?waitUntil then yeah, you should always await or the Worker can be finished with the response before it has written to KVn will show the new value.I'm seeing situations where customers from other regions hit my endpoint and the KV lookup returns nothing, but if I have them a few minutes later, they can access the object as expected.
Initial reads from a location do not have a cached value. The data must be read from the nearest central data store, resulting in a slower response.
200, <key/uuid>ctx.waitUntilwaitUntilwaitUntilwaitUntilwaitUntiln200, <key/uuid>