Hi @wanton badger. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Does Vercel Deployment clear ALL caches?
wind ermineBOT
The knowledge sources do not explicitly state how Vercel handles all Nuxt-related caches on redeploy, so I can’t give a definitive yes/no.
From the Nuxt side:
- Nuxt’s hybrid rendering caches (ISR/SWR via
routeRules) are tied to the deployment and CDN/platform cache. ISR content on Vercel is documented as “persists until the next deploy,” which implies that a new deployment invalidates those cached responses. [Route rules] - Nuxt also has its own data caching for
useAsyncData/useFetch, which you can explicitly clear at runtime withclearNuxtData, but that’s per-request/app-instance, not a long‑lived platform cache. [clearNuxtData] - Nitro/Unstorage can use platform-specific drivers like Vercel Runtime Cache or Vercel Blob, which are separate storage layers. The Unstorage docs describe how to use them but do not say they are automatically cleared on deploy. [Vercel driver]
What this means for your situation, based only on the docs:
- Nuxt’s ISR/SWR HTML/payload caches should be refreshed on a new Vercel deployment.
- There is no explicit documentation in these sources that all other caches or storage (e.g. Unstorage with
vercel-runtime-cache,vercel-blob, or any Supabase/PostHog–side caching) are automatically cleared by a Vercel redeploy.
Given your error is coming from a Supabase cron calling a Nitro API route, and the column now exists, the docs here don’t provide enough information to confirm whether:
- Vercel is still running an old function build,
- some Unstorage/Vercel runtime cache is serving stale data, or
- Supabase itself is using a cached query plan/schema.
From these sources alone, the safest conclusion is:
- Nuxt’s documented hybrid rendering caches are reset on deploy,
- but you cannot rely on a Vercel redeploy to clear every possible cache/storage layer, and the docs here don’t guarantee that behavior.
If you need to be certain at the Nuxt level, you can:
- Avoid long-lived ISR/SWR on that API route (no
isr/swrrule for it). [Route rules] - Avoid using Unstorage’s Vercel runtime cache for that endpoint, or explicitly clear entries if you do. [Vercel driver]