Skip to content
Closed
Changes from all commits
Commits
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
2 changes: 2 additions & 0 deletions docs/01-app/02-guides/how-revalidation-works.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,8 @@ In the [cache handler API](/docs/app/api-reference/config/next-config-js/cacheHa

## Multi-Instance Considerations

> **Note:** Revalidation is instance-local by default.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

And once again, is this not the very same thing said in line 59? What is the problem you are trying to solve here.


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