Skip to content

docs: clarify instance-local revalidation behavior in multi-instance … #92403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Akash504-ai wants to merge 2 commits into from
+2 −0
Closed

docs: clarify instance-local revalidation behavior in multi-instance … #92403

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
65ea87e
docs: clarify instance-local revalidation behavior in multi-instance …
Akash504-ai Apr 6, 2026
952eab8
docs: simplify note to avoid duplication in multi-instance section
Akash504-ai Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/01-app/02-guides/how-revalidation-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,12 @@ In the [cache handler API](/docs/app/api-reference/config/next-config-js/cacheHa

## Multi-Instance Considerations

> ⚠️ **Important:** In multi-instance or serverless environments (such as deployments on Vercel), revalidation is instance-local by default.
Copy link
Copy Markdown
Member

@icyJoseph icyJoseph Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is repeating the first sentence on 63 no? and the platform mentioned here, does handle this already.

>
> Calling `revalidateTag()` or `revalidatePath()` only invalidates the cache on the instance handling the request. Other instances may continue serving stale content until they receive the invalidation event through a shared cache or coordination mechanism.
Copy link
Copy Markdown
Member

@icyJoseph icyJoseph Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Repeats the second sentence on 63, only adding revalidatePath

>
> To ensure consistent revalidation across instances, you should configure a shared cache handler (for example, using Redis or another external store).
Copy link
Copy Markdown
Member

@icyJoseph icyJoseph Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ### Multi-instance with shared cache section mentions this though - and the Redix example is actually linked further down


When running multiple Next.js instances behind a load balancer, revalidation events are local by default. Calling `revalidateTag()` on instance A only invalidates the cache on that instance. Other instances continue serving the stale content until they learn about the invalidation.

The cache handler API provides two hooks for distributed coordination:
Expand Down
Loading