This page is hosted on AWS Amplify
Content is cached with a 60-second TTL. On-Demand ISR is not supported — even if Sanity publishes a webhook, this page cannot respond to it. Stale content is served until the TTL expires.
checkffff
checkingfbxvfdvdfdvdv
Sanity published at: 06:15:32 am
Why This Page Can't Update Instantly
Sanity publishes new content
An editor publishes updated content in Sanity Studio. Sanity fires a webhook to "/api/revalidate".
Webhook arrives — but nothing happens
AWS Amplify receives the webhook call. Next.js runs revalidateTag() inside the route handler, but Amplify's infrastructure does not honour on-demand cache invalidation. The call is silently ignored.
Page waits for 60-second TTL to expire
Only after the 60-second time-based cache expires will the next visitor trigger a fresh Sanity fetch. During those 60 seconds, all visitors see stale content.
On Vercel: step 2 works — cache is invalidated instantly
Vercel's infrastructure fully supports revalidateTag() with { expire: 0 }. The very next request after the webhook fires serves fresh content from Sanity.
