💥 feat(sdk): Support Standalone Activities by maciejdudko · Pull Request #1402 · temporalio/sdk-rust

maciejdudko · 2026-07-14T16:29:18Z

💥 Breaking changes

ActivityInfo fields related to the containing workflow are made optional.
async_activity_handle::ActivityIdentifier::ById is split into ByIdWorkflow and ByIdStandalone.

What was changed

Added support for executing Standalone Activities in SDK Worker.
Added high-level client interfaces for starting and interacting with Standalone Activities.

Why?

Feature request: temporalio/features#706

Checklist

Closes [Feature Request] Support standalone activities #1070
How was this tested:

Added tests in crates/sdk-core/tests/integ_tests/standalone_activity_tests.rs

Any docs updates needed?

SAA guide for Rust needs to be added here: https://docs.temporal.io/standalone-activity

Sushisource

Awesome to see this ready!

Sushisource · 2026-07-23T16:50:25Z

+/// To support deserialization of transmitted payloads, the object internally stores a reference
+/// to the client used to make the request. For this reason, this type is parametrized with client
+/// type. The client reference can be dropped by calling [`simple`](Self::untyped).


This comment looks like it's not accurate any more since just a dataconverter, not a whole client, is stored (which is good).

Sushisource · 2026-07-23T16:51:46Z

+    /// True if activity input is present.
+    /// See [`ActivityDescribeOptions::include_input`](crate::ActivityDescribeOptions::include_input).
+    /// Use [`input`](Self::input) or [`raw_input`](Self::raw_input) to retrieve it.
+    pub fn has_input(&self) -> bool {
+        self.raw_input.is_some()
+    }


Nit: IMO we don't need this - easy enough to just call raw_input().is_some()

I'd keep these methods for symmetry with heartbeat_details/last_failure, also I don't like making users call raw_* methods when they're not interested in raw payloads.

Sushisource · 2026-07-23T16:52:18Z

+    /// True if activity outcome is present.
+    /// See [`ActivityDescribeOptions::include_outcome`](crate::ActivityDescribeOptions::include_outcome).
+    /// Use [`outcome`](Self::outcome) or [`raw_outcome`](Self::outcome) to retrieve it.
+    pub fn has_outcome(&self) -> bool {


Sushisource · 2026-07-23T17:59:26Z

+pub enum ActivityResultError {
+    /// Activity execution did not complete successfully.
+    #[error("Activity failed: {0}")]
+    ActivityFailed(#[source] IncomingError),


With WorkflowGetResultError we distinguish Failed / timedout / cancelled etc at the top level, probably makes sense to do that here too.

Sushisource · 2026-07-23T18:00:53Z

+                .await?
+                .into_inner();
+
+            // If resp.outcome.value is None, poll again


Will this hot-loop?

The server uses long-poll for this request.

Sushisource · 2026-07-23T18:07:21Z

+    /// Start a standalone activity and wait for its result.
+    ///
+    /// Equivalent to `start_activity(...).await?.result()`.
+    pub async fn execute_activity<A>(


We don't have execute_workflow, personally not a big fan of these simple sugars.

Going to remove it for now since it can always be added later.

Sushisource · 2026-07-23T18:08:38Z

+    ///
+    /// To get a handle that can be used to complete an activity asynchronously,
+    /// see [`get_async_activity_handle`](Self::get_async_activity_handle).
+    pub fn get_untyped_activity_handle(


Same here, I think just calling get_activity_handle<UntypedActivity>(...) is fine and we can say how to do that in the docstring.

get_activity_handle requires the activity as argument. get_untyped_activity_handle does not. get_activity_handle::<UntypedActivity> would not work.

Ah, yeah, I just wrote it wrong though - you can still just pass UntypedActivity as the arg.

...though I guess that does require you to pointlessly specify a name, so, that being the case I'm fine with this then

Sushisource · 2026-07-23T18:12:35Z

+/// Activity options. Specifying at least one of them is required, but specifying both is also
+/// allowed. Note that this type does not cover all available timeout options for an Activity.
+#[derive(Debug, Clone, Copy, PartialEq, Eq)]
+pub enum ActivityCloseTimeoutOptions {


IMO no reason to add the "options" postfix here

Sushisource · 2026-07-23T18:13:52Z

+    pub id: String,
+    /// Combined schedule-to-close and start-to-close timeout options. At least one of them is
+    /// required.
+    #[builder(setters(name = combined_close_timeouts, vis = ""))]


This is part of the start_fn when starting from a workflow, and it should be here too IMO, that simplifies a lot of other stuff.

The "combined" wording in the docstring / setter (which can go away if we make it part of constructor) diverges from the workflow version too, I think we can keep it the same.

This setter is private. The idea is that the user does not use combined_close_timeouts or ActivityCloseTimeoutOptions directly - instead, they use either schedule_to_close_timeout or start_to_close_timeout to set one of them, or close_timeouts to set both.

Ah. I didn't see it was private. Regardless... I still think it makes sense to just do exactly what the workflow version does. Passing the right variant to close_timeouts is easy

Sushisource · 2026-07-23T18:16:39Z

@@ -0,0 +1,15 @@
+use std::error::Error;
+
+pub(crate) fn try_into_or_box_err<A, B, E, MapErr>(


Since it's only used from client lib, can probably just stick it in there as private.

maciejdudko force-pushed the standalone-activities branch 9 times, most recently from 49d89b7 to dd726c2 Compare July 22, 2026 17:55

Support Standalone Activities

bbcf171

maciejdudko force-pushed the standalone-activities branch from dd726c2 to bbcf171 Compare July 23, 2026 16:02

maciejdudko changed the title ~~feat(sdk): support Standalone Activities~~ 💥 feat(sdk): Support Standalone Activities Jul 23, 2026

maciejdudko marked this pull request as ready for review July 23, 2026 16:10

maciejdudko requested a review from a team as a code owner July 23, 2026 16:10

Sushisource reviewed Jul 23, 2026

View reviewed changes

		@@ -0,0 +1,15 @@
		use std::error::Error;

		pub(crate) fn try_into_or_box_err<A, B, E, MapErr>(

Uh oh!

Conversation

maciejdudko commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💥 Breaking changes

What was changed

Why?

Checklist

Uh oh!

Sushisource left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

maciejdudko Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Sushisource Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

maciejdudko commented Jul 14, 2026 •

edited

Loading

maciejdudko Jul 28, 2026 •

edited

Loading

Sushisource Jul 28, 2026 •

edited

Loading