hey there - has the behavior with KV changed recently? we are getting KV hits for deleted key-pairs
hey there - has the behavior with KV changed recently? we are getting KV hits for deleted key-pairs
some context:
- the key has a cacheTTL of 24h
- we delete the key through the REST API
- the key is not in the KV if i prefix search the key on the dashbaord
- a console.log() after the read in the worker still finds the old row
so I'm thinking either the delete is just taking longer than usual to propagate, or maybe something's changed, cause iirc we got a miss here previously
0 Replies