Vercel Blob now supports consistent reads on private storage
Vercel Blob now supports consistent reads on private storage by passing useCache: false to get() or presignUrl(). This bypasses the CDN to ensure reads reflect the latest write, useful for time-sensitive data like agent memory files and session transcripts, though such reads take longer and incur Fast Origin Transfer charges.
now supports consistent reads on private storage. Pass to or for a read that reflects the latest write.Vercel BlobuseCache: falseget()presignUrl()
A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing pathname, readers might see the cached version for up to 60 seconds.
When a read must reflect the latest write, like an agent's memory file, a session transcript, or a scheduled JSON report, pass . These reads bypass the CDN, take longer than cached reads, and incur .useCache: falseFast Origin Transfer
You can also bypass the cache without the SDK. Under the hood, adds a query parameter to the request. You can set it yourself on a private blob URL:useCache: falsecache=0
Install the latest SDK for consistent reads:@vercel/blob
Learn more in the .consistent reads documentation
Source: original entry ↗