Clarify Nexus failover behavior when the Handler Namespace fails over#4934
Draft
stephanos wants to merge 1 commit into
Draft
Clarify Nexus failover behavior when the Handler Namespace fails over#4934stephanos wants to merge 1 commit into
stephanos wants to merge 1 commit into
Conversation
Rework the 'What to expect on failover' section to explain the case where the Handler Namespace fails over before the completion callback is delivered while the Caller Namespace stays put: the callback is durable Handler-Workflow state that re-drives from the new active Cluster, and each Namespace resolves its active Cluster independently, so the callback still reaches the Caller. Update the diagram to depict this asymmetric case. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
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
1 participant
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
Reworks the What to expect on failover section of the self-hosted Nexus page to clearly explain the case where the Handler Namespace fails over before the completion callback is delivered (while the Caller Namespace stays on its Cluster) — the question that came up after the original PR merged.
Why
The original diagram (merged in #4906) only showed both Namespaces failing over together, which obscured that callback delivery targets the Caller Namespace's active Cluster independently of where the Handler runs.
Mermaid lint passes.
🤖 Generated with Claude Code
┆Attachments: EDU-6773 Clarify Nexus failover behavior when the Handler Namespace fails over