I know I saw this in here before but

I know I saw this in here before but cant seem to find any resolution to it... I'm currently getting errors saying my cursor is invalid and not sure how to fix

My code looks like so:

let cursor: string | undefined, complete = false

do {
    const { keys, list_complete, cursor: cur } = await env.Tracking.list<R2LatencyMetadata>({ cursor, prefix: 'TimeSeries/R2' })

    complete = list_complete, cursor = cur

    // Do some things with keys
} while (!complete && cursor)

let cursor: string | undefined, complete = false

do {
    const { keys, list_complete, cursor: cur } = await env.Tracking.list<R2LatencyMetadata>({ cursor, prefix: 'TimeSeries/R2' })

    complete = list_complete, cursor = cur

    // Do some things with keys
} while (!complete && cursor)

UnsmartOP•8/9/22, 12:37 AM

Seems like I am still getting errors sometimes but a lot less than when I originally posted the above.

Just had a request fail saying to following cursor is invalid if it helps (kv 7a23d30e52584ab3bb7e435dc46425b7):

UnsmartOP•8/9/22, 6:11 PM

@walshydev sorry for the ping but I assume I am doing nothing wrong and I still get these errors saying my cursor is invalid with the above code. Curious if you would be able to ping the right people for this

UnsmartOP•8/9/22, 6:12 PM

Its like ~5-10% of requests that fail currently

Walshy•8/9/22, 6:12 PM

I'd probably ping @kian for this tbh LuL

kian•8/9/22, 6:13 PM

UnsmartOP•8/9/22, 6:17 PM

If it helps also anytime it fails its always the second page the (the first one that actually has a cursor) at least that I have seen

WWalshy I'd probably ping @kian for this tbh <:LuL:353601651229065216>

kian•8/9/22, 6:23 PM

i'd assume cursors are just an opaque string - but if anyone had the tools to see what the error was it's you not me :^)

kian•8/9/22, 6:23 PM

however it appears that I can't test much anyways since KV throws a 429 at me for a namespace with like 5 keys

UnsmartOP•8/9/22, 6:25 PM

Yeah I get 429s every once in a while in waves also dont really track that though. Easier to see the cursor failing since I run it on a cron and it throws an error I can see on my worker summary