Skip to content

Commit 4f8ffe6

Browse files
stephanosclaude
andcommitted
Use a flowchart with Cluster subgraphs for the failover diagram
The CI mermaid linter parses headless (no DOM) and can't handle sequence 'box'. A flowchart with subgraphs shows the same Cluster boxes containing the Namespaces and passes the linter. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 7f04fe6 commit 4f8ffe6

1 file changed

Lines changed: 11 additions & 14 deletions

File tree

docs/production-deployment/self-hosted-guide/temporal-nexus.mdx

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -130,20 +130,17 @@ Cluster, the completion callback is delivered to the caller Namespace's current
130130
active Cluster, re-resolved on each attempt:
131131

132132
```mermaid
133-
sequenceDiagram
134-
box Cluster A
135-
participant caA as Caller Namespace
136-
participant haA as Handler Namespace
133+
flowchart LR
134+
subgraph A["Cluster A (initially active)"]
135+
caA["Caller Namespace"]
136+
haA["Handler Namespace"]
137137
end
138-
box Cluster B
139-
participant caB as Caller Namespace
140-
participant haB as Handler Namespace
138+
subgraph B["Cluster B (active after failover)"]
139+
caB["Caller Namespace"]
140+
haB["Handler Namespace"]
141141
end
142-
Note over caA,haA: Cluster A active
143-
caA->>haA: start Nexus Operation
144-
haA-->>caA: Operation started, token returned
145-
Note over caA,haB: 💥 Fail over both namespaces from Cluster A to B
146-
Note over caB,haB: Cluster B active
147-
haB->>caB: deliver completion callback
148-
Note over caB: Nexus Operation completes
142+
caA -->|"1 start Nexus Operation"| haA
143+
caA -. replicated .- caB
144+
haA -. replicated .- haB
145+
haB -->|"2 completion callback, after failover"| caB
149146
```

0 commit comments

Comments
 (0)