bummer. alright! is there any plan to integrate this?
bummer. alright! is there any plan to integrate this?
cacheTtl field of KVNamespace.get’s option. cacheTtl & expirationTtl are frequently confused for each other.
KV GET failed: 500 Internal Server Error getting this error again in Asia Regionwrangler kv:key list to dump the key values and metadata too?jti in cloudflare KV? I've heard that KV has high latency on cross region access, which could take 60s to propagate data to other region. My service provide token for users to use in their server, which could be placed in a different region from where the token is generatedjti in KV with a TTL (or cache data in general). jti will be retrieved in every requests, so low latency and low cost is a very important. My old implementation on my onprem server is deploying a redis cluster, with each redis instance will sit next to the main service in every region for lowest latency. I only write data once, rarely update it and access it many times in its life timejti value? If its often then KV will be great because it caches data in the colo it gets requested from so it will be pretty fast. For me I generally get around ~40-50ms on cache hits iirc.

api.cloudflare.com) to interact with KV or through a Worker? Does this happen consistently when requested in a specific way or from a specific location? And finally, are you able to share the full JSON output you get from the API? Thanks!
cacheTtlcacheTtlKVNamespace.getexpirationTtlKV GET failed: 500 Internal Server Errorwrangler kv:key listjtijtijtijtiapi.cloudflare.com