Suggestion: when KV read quotas are full, still allow KV reads during builds

Feedback
1

hi,

Loving Vercel, next.js, and learning KV stores.

I hit my daily limit and the site broke.

I’m using getStaticProps now - which is working great.

What would be very nice is if I could build a new deployment to refresh the static props so the site can still work even when my KV read usage is fully exhausted.

This would just be 1 more read per hour but keeps everything alive.

It’s unlikely this would be abused because you’d hit your build usage limits pretty quickly.

1 Like
3

Thanks for sharing your feedback, @wayneschuller! I’ve shared it with the team.

1 Like
4

Thank you. For the second day in a row, I’ve hit my daily KV usage limit (3000 requests).

My actual app, when deployed, uses static props with 10-minute revalidation, so that does not cause significant usage.

I use the app in my local dev environment where next.js rightly doesn’t cache the static props but gets them fresh from the KV store each time. A day of coding has just used up all my quota. Maybe I’ll hack it so that in local dev it uses dummy data.

But in the meantime, it would be great if the deployment builds could get ‘out of quota’ access to the KV store to get the site built.