docs: clarify instance-local revalidation behavior in multi-instance …#92403
Open
Akash504-ai wants to merge 1 commit intovercel:canaryfrom
Open
docs: clarify instance-local revalidation behavior in multi-instance …#92403Akash504-ai wants to merge 1 commit intovercel:canaryfrom
Akash504-ai wants to merge 1 commit intovercel:canaryfrom
Conversation
Collaborator
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Adds a clear warning in the "Multi-Instance Considerations" section to highlight that revalidation is instance-local by default in multi-instance or serverless environments.
Why?
While the behavior is already explained later in the section, it is not immediately obvious to most users—especially those deploying on serverless platforms like Vercel.
This can lead to confusion, as developers may assume that
revalidateTag()orrevalidatePath()invalidates cache globally across all instances, when in reality it only affects the instance handling the request.How?
Fixes #92402