From 232d36809affca7cf1488056028d6dc17e69a1f9 Mon Sep 17 00:00:00 2001 From: Jwahir Sundai Date: Wed, 15 Jul 2026 13:41:39 -0500 Subject: [PATCH] sano links --- docs/encyclopedia/nexus/nexus-operations.mdx | 1 + docs/encyclopedia/nexus/nexus.mdx | 1 + docs/encyclopedia/temporal-client.mdx | 4 +++- 3 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/encyclopedia/nexus/nexus-operations.mdx b/docs/encyclopedia/nexus/nexus-operations.mdx index cb307dc67c..b87ed51392 100644 --- a/docs/encyclopedia/nexus/nexus-operations.mdx +++ b/docs/encyclopedia/nexus/nexus-operations.mdx @@ -47,6 +47,7 @@ An Operation's lifecycle spans scheduling, reliable delivery with retries, handl ::: **Caller side:** A caller Workflow executes a Nexus Operation through a [Nexus Endpoint](/nexus/endpoints) using the Temporal SDK. +A [Standalone Nexus Operation](/standalone-nexus-operation) is a top-level Nexus Operation Execution started directly by a Client, without using a caller Workflow. **Handler side:** [Nexus Services](/nexus/services) and their Operations are registered with a Worker that polls the Endpoint's target Task Queue. Operations are defined using SDK builder functions: diff --git a/docs/encyclopedia/nexus/nexus.mdx b/docs/encyclopedia/nexus/nexus.mdx index f60a195248..62ed4dd4c5 100644 --- a/docs/encyclopedia/nexus/nexus.mdx +++ b/docs/encyclopedia/nexus/nexus.mdx @@ -49,6 +49,7 @@ Caller and handler Workflows are siblings that communicate across Namespace boun A [Nexus Service](/nexus/services) is a named collection of [Nexus Operations](/nexus/operations) that a team exposes. Operations abstract the underlying implementation - callers don't need to know whether an Operation starts a Workflow, sends a Signal, runs a Query, or executes other reliable code. +If you need to orchestrate multiple Nexus Operations, call them from a Workflow. But if you just need to execute a single Nexus Operation across Namespace boundaries, use a [Standalone Nexus Operation](/standalone-nexus-operation). The [Operation lifecycle](/nexus/operations#operation-lifecycle) supports two modes: diff --git a/docs/encyclopedia/temporal-client.mdx b/docs/encyclopedia/temporal-client.mdx index bcdff87294..9ac763738f 100644 --- a/docs/encyclopedia/temporal-client.mdx +++ b/docs/encyclopedia/temporal-client.mdx @@ -26,8 +26,10 @@ The most common operations that a Temporal Client allows you to perform are the - Query a Workflow Execution - Signal a Workflow Execution - Start and manage [Standalone Activities](/standalone-activity) directly, without involving a Workflow +- Start a [Standalone Nexus Operation](/standalone-nexus-operation) directly, without using a caller Workflow -A Standalone Activity is a top-level [Activity Execution](/activity-execution) started directly by a [Client](/encyclopedia/temporal-sdks#temporal-client), without using a Workflow. +A Standalone Activity is a top-level [Activity Execution](/activity-execution) started directly by a Client, without using a Workflow. +A Standalone Nexus Operation is a top-level [Nexus Operation Execution](/nexus/operations) started directly by a Client, without using a caller Workflow. ## SDK guides {/* #sdk-guides */}