Skip to content

sano links #4890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jsundai merged 3 commits into from
Jul 16, 2026
Merged

sano links #4890

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
232d368
sano links
jsundai Jul 15, 2026
faf4167
Merge branch 'main' into sano-links
jsundai Jul 15, 2026
eb5b5a7
Merge branch 'main' into sano-links
jsundai Jul 16, 2026
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
1 change: 1 addition & 0 deletions docs/encyclopedia/nexus/nexus-operations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
1 change: 1 addition & 0 deletions docs/encyclopedia/nexus/nexus.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
4 changes: 3 additions & 1 deletion docs/encyclopedia/temporal-client.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 */}

Expand Down