Skip to content

Add Standalone Activities feature reference #105

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

Open
donald-pinckney wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add Standalone Activities feature reference #105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0f3d87
Add Standalone Activities feature reference
donald-pinckney May 1, 2026
fe85808
plans
donald-pinckney May 6, 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
56 changes: 56 additions & 0 deletions AUTHORING_LOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
# Authoring Log

## Standalone Activities feature (added per `STANDALONE_ACTIVITIES_AUTHORING_PLAN.md`)

Six new reference files plus a surgical `SKILL.md` edit. Each reference file was authored by an isolated subagent that read only the docs paths assigned to it (no cross-reading of sibling reference files).

### `references/core/standalone-activities.md`
- **Docs consulted:** `docs/encyclopedia/activities/standalone-activity.mdx` (primary), `docs/cloud/metrics/openmetrics/metrics-reference.mdx` (line 315, for the no-new-metric-names claim). Supporting files (`activities.mdx`, `activity-execution.mdx`, `job-queue.mdx`) referenced by link only.
- **Citations:** 26 inline.
- **VERIFY markers:** 0.
- Self-checks passed: `TerminateExisting` / `TerminateIfRunning` listed only as unsupported; pause/reset/update-options listed only as unsupported; CLI v1.7.0+ / Server v1.31.0+ stated verbatim; separate ID space; dual-use claim preserved verbatim; no invented metric names; no TypeScript link.

### `references/core/standalone-activities-cli.md`
- **Docs consulted:** `docs/cli/activity.mdx` (full file), `docs/encyclopedia/activities/standalone-activity.mdx` (lines 23, 109–114, 135–138).
- **Citations:** 50 inline. 323 lines.
- **VERIFY markers:** 0.
- All 14 `temporal activity` subcommands have their own H3 headings. Public Preview gaps (`pause`, `reset`, `update-options`) flagged at top and at each subcommand. `unpause` annotated since it only operates on paused Activities, which Standalone Activities cannot enter in Public Preview. Global Flags referenced by line range, not transcribed.

### `references/python/standalone-activities.md`
- **Docs consulted:** `docs/develop/python/activities/standalone-activities.mdx` only.
- **Citations:** 30 inline.
- **VERIFY markers:** 2.
1. Server v1.31.0+ requirement is not stated in the Python doc (only CLI v1.7.0+ and Python SDK v1.23.0+ are stated there). The encyclopedia is the source for the server-version pairing.
2. The Python doc does not show conflict-policy / reuse-policy kwargs on `start_activity` (`USE_EXISTING`, `REJECT_DUPLICATES`, etc.). Per methodology, no kwargs were invented; policy semantics deferred to `references/core/standalone-activities.md`.
- Methods/kwargs used: `client.execute_activity`, `client.start_activity`, `client.get_activity_handle`, `activity_handle.result`, `client.list_activities`, `client.count_activities`, `ClientConfig.load_client_connect_config`. Cloud auth limited to mTLS + API key (env-var modes).

### `references/go/standalone-activities.md`
- **Docs consulted:** `docs/develop/go/activities/standalone-activities.mdx` (primary), `docs/encyclopedia/activities/standalone-activity.mdx` (versions + Public Preview limitations only).
- **Citations:** 33 inline. ~270 lines.
- **VERIFY markers:** 1. The Go doc does not show the exact field name on `StartActivityOptions` for conflict policy / reuse policy, nor the Go enum constants for `USE_EXISTING` / `REJECT_DUPLICATES`. The encyclopedia lists the policy values but Go-specific binding names need confirmation against the godoc before adding a code snippet.
- APIs verbatim from the Go doc: `ExecuteActivity`, `GetActivityHandle`, `ListActivities`, `CountActivities`, `StartActivityOptions`, `GetActivityHandleOptions`, `ListActivitiesOptions`, `CountActivitiesOptions`, handle methods `Get`/`GetID`/`GetRunID`.

### `references/java/standalone-activities.md`
- **Docs consulted:** `docs/develop/java/activities/standalone-activities.mdx` (primary), `docs/encyclopedia/activities/standalone-activity.mdx` (versions + Public Preview limitations only).
- **Citations:** 33 inline (32 to the Java doc, 4 to the encyclopedia — some overlap).
- **VERIFY markers:** 1. The Java doc does not show builder methods on `StartActivityOptions` for conflict policy / reuse policy. Policy values documented as concepts; Java setter names not invented.
- Prereqs documented: Java 8+, Java SDK v1.35.0+, CLI v1.7.0+, Server v1.31.0+. Cloud auth limited to mTLS and API key.

### `references/dotnet/standalone-activities.md`
- **Docs consulted:** `docs/develop/dotnet/activities/standalone-activities.mdx` (primary), `docs/encyclopedia/activities/standalone-activity.mdx` (versions + Public Preview limitations only).
- **Citations:** 32 inline (28 to the .NET doc, 4 to the encyclopedia).
- **VERIFY markers:** 1. The .NET doc does not show a code snippet wiring `USE_EXISTING` / `REJECT_DUPLICATES` into `StartActivityOptions`; the specific .NET option property names are not present. Documented the supported policy values (from the encyclopedia) and the unsupported `TerminateExisting` / `TerminateIfRunning` limitation, without inventing .NET property names.
- APIs verbatim from the .NET doc: `ExecuteActivityAsync`, `StartActivityAsync`, `GetActivityHandle`, `GetResultAsync`, `ListActivitiesAsync`, `CountActivitiesAsync`, `StartActivityOptions`, `[Activity]`, `TemporalWorker`, `TemporalWorkerOptions`, `AddActivity`, `ClientEnvConfig.LoadClientConnectOptions`, `ActivityExecution`. Cloud auth limited to mTLS and API key.

### `SKILL.md` edit
- Added a "Standalone Activities" section just above "Task Queue Priority and Fairness", pointing at the six new reference files and noting that TypeScript SDK coverage is upstream-pending.
- No other changes to existing sections; skill version field left at `0.3.2` (no user request to bump).

### Cross-cutting VERIFY summary

The five language/CLI subagents converged on a single shared gap: **the per-language docs do not yet show conflict-policy / reuse-policy parameter wiring** (Python kwargs, Go fields, Java builders, .NET options). The encyclopedia lists the policy values (`USE_EXISTING`, `REJECT_DUPLICATES`; with `TerminateExisting` / `TerminateIfRunning` unsupported in Public Preview). Recommended follow-up: when the SDK docs add policy snippets (or when the API surface is confirmed against the per-language godoc/javadoc/etc.), revisit the four language references and resolve the VERIFY markers.

### Files NOT modified

- `references/typescript/` — intentionally untouched. No upstream Standalone Activities doc exists.
- `references/python/advanced-features.md`, `references/go/advanced-features.md`, etc. — left as-is. The plan reserved the option to add a one-line cross-link, but the SKILL.md "Standalone Activities" section already provides the discovery path; no edit was needed.
15 changes: 15 additions & 0 deletions SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,21 @@ Check if `temporal` CLI is installed. If not, follow the instructions at `refere
- **`references/core/ai-patterns.md`** - AI/LLM pattern concepts
- Language-specific info at `references/{your_language}/ai-patterns.md`, if available. Currently Python only.

## Standalone Activities

Standalone Activities are Temporal's [Public Preview](https://docs.temporal.io/evaluate/development-production-features/release-stages#public-preview) job-queue primitive: a single Activity executed directly by a Client as a top-level execution, without a Workflow. Use them when you only need to run **one** Activity reliably (send an email, process a webhook, sync data, etc.) — for orchestrating multiple Activities, use a Workflow. The same Activity Function runs as a Standalone Activity or a Workflow Activity with no code changes.

Requires Temporal CLI v1.7.0+ and Temporal Server v1.31.0+. Public Preview in Temporal Cloud.

- **`references/core/standalone-activities.md`** — concept, when-to-use, dual-use with Workflows, conflict/reuse policies, Public Preview limitations, observability, Cloud support
- **`references/core/standalone-activities-cli.md`** — `temporal activity` CLI subcommand reference (`start`, `execute`, `result`, `list`, `count`, `describe`, `cancel`, `terminate`, etc.)
- Per-language quickstarts and APIs:
- **`references/python/standalone-activities.md`**
- **`references/go/standalone-activities.md`**
- **`references/java/standalone-activities.md`**
- **`references/dotnet/standalone-activities.md`**
- TypeScript SDK: not yet covered upstream — point users at the Python or Go reference for now.

## Task Queue Priority and Fairness

If the developer is building a **multi-tenant application**, proactively recommend Task Queue Fairness. Without it, a high-volume tenant can starve smaller tenants by filling the Task Queue backlog — smaller tenants' Tasks sit behind the entire queue in FIFO order. Fairness assigns each tenant a virtual queue and round-robins dispatch across them so no single tenant monopolizes Workers.
Expand Down
Loading