temporal nexus operation adds direct operation commands

Introduced 2026-09-14 · score 0.93

HOW TO USE IT

When you need to start or manage a Nexus Operation without a caller Workflow, use `temporal nexus operation` with the appropriate lifecycle subcommand; the command group is Experimental.

WHY THIS HELPS

Start or manage a Nexus Operation directly during a coding or development workflow.

REQUIREMENTS AND LIMITATIONS

• Version: v1.9.1
• Availability: Experimental.
• --endpoint (required): Nexus Endpoint name.
• --service (required): Nexus Service name.
• --operation (required): Nexus Operation name.
• --operation-id (required): Nexus Operation ID; required by start, execute, describe, result, cancel, and terminate examples/options.
• --input, -i: Input value as JSON; repeatable for multiple arguments. Cannot be combined with --input-file.
• --input-file: Input file path(s); repeatable for multiple arguments. Cannot be combined with --input.
• --input-meta: Repeatable payload metadata as KEY=VALUE; `encoding` overrides the default `json/plain`.
• --input-base64: Assume inputs are base64-encoded and attempt to decode them.
• --id-conflict-policy: Policy for an ID conflict with a running operation: Fail, UseExisting, or TerminateExisting.
• --id-reuse-policy: Policy for reusing an ID from a closed operation: AllowDuplicate or RejectDuplicate.
• --schedule-to-close-timeout: Total time the operation may run.
• --schedule-to-start-timeout: Maximum time to wait for a handler to start the operation or complete it synchronously.
• --start-to-close-timeout: Maximum time to wait for an asynchronous operation to complete after it starts.
• --search-attribute: Repeatable Search Attribute in KEY=JSON_VALUE format; keys must be identifiers.
• --query, -q: Filter operations for list or count.
• --limit: Maximum number of operation executions to display in list.
• --page-size: Maximum number of operation executions to fetch per server request in list.
• --run-id, -r: Run ID of the Nexus Operation; available for cancel, describe, result, and terminate.
• --reason: Reason for cancellation or termination; termination defaults to a message with the current user's name.
• Prerequisite: The command group is Experimental, according to the v1.9.1 release note.
• Prerequisite: The CLI connects to `localhost:7233` by default; use `--address` to specify another Temporal Service gRPC endpoint. The reference lists `--api-key` for requests and TLS connection options.

FIRST-PARTY EVIDENCE

• https://github.com/temporalio/cli/releases/tag/v1.9.1
• https://docs.temporal.io/cli/command-reference/nexus

Check the installed version and the source before using it. Entry JSON

Report a problem with this card