KV giving null while doing get even though the key exists
There is no error from KV and also there is no response with correct value.
JYou'll probably need to give us more context on the problem. Do you have a code sample or something? Are you testing locally or are you working in production?
AProduction
A@JustinNoel The code snippet is as follows:
Here is the sample code... Sometimes, I'm getting null in the
Here is the sample code... Sometimes, I'm getting null in the
then part of the response, not the catch part. So the request is successful while the return response from kv is null even though there is value for the said key
HErrors are only thrown when something goes wrong internally. Since a
getAlso, you seem to be combining await and then
JAre you testing locally or are you working in production?
AThe key itself is present and has value in kv store
AMistake on my part
AProduction
HNo, I just meant that, if a key wasn't present, that wouldn't be an error, so it wouldn't hit the
catch handler.HHow long has it been since it was inserted/updated? Updates can take 60 seconds or more to show up, depending on how recently you tried to access the key, and what
cacheTtl you set, if any.ARight
AAbout 1 week
JTry just doing this:
If you to catch errors, I would suggest using a try catch instead of then and catch.
If you to catch errors, I would suggest using a try catch instead of then and catch.
AI'm not getting error. The kv is just returning null even though value for the key exists
MHow do you know it exists?
VBy directly checking in the KV store, by searching with the key
JIs
KV_NAME bound to the correct KV namespace?AYes
TCan you sanity check that by adding something in the KV web view and then trying to retrieve it in your code? I very much suspect there is an issue on your side somewhere.
AI did do that too... No dice
