Skip to content

Honor explicit abandonment in the in-process test host #814

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
wangbill (YunchuWang) wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Honor explicit abandonment in the in-process test host #814

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
7c6ab0d
Honor explicit abandonment in the in-process test host
YunchuWang Oct 9, 2026
8e2f5fb
Preserve accepted completion after late test-host send failures
YunchuWang Oct 9, 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
20 changes: 20 additions & 0 deletions src/InProcessTestHost/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,26 @@ PurgeResult purgeResult = await testHost.Client.PurgeAllInstancesAsync(
creation-time range. You can provide `CreatedTo` without `CreatedFrom`. Explicit
bounds are inclusive and are evaluated in UTC.

## Explicit Work-Item Abandonment

The in-process sidecar honors explicit worker abandonment of activity and orchestration
work items. Abandonment cancels that delivery's pending execution, allowing the existing
dispatcher to release and requeue the work item for another attempt.

Each delivery has a fresh completion token in the existing gRPC `completionToken` field.
Completion and abandonment requests must echo that token. Missing tokens return
`InvalidArgument`; unknown or already settled tokens return `NotFound`. Duplicate
abandonment and late completion cannot affect a replacement delivery. Abandoning an
orchestration also discards its partial response actions and releases its temporary
worker history snapshot, without deleting committed history.

An accepted completion takes precedence over a later failure of that delivery's pending
stream write. The send failure cannot replace the accepted result or requeue completed work.

Closing the `GetWorkItems` stream does **not** implicitly abandon work that was already
delivered. An activity can still finish and send its completion through an independent
RPC. This behavior does not add an activity timeout, heartbeat, or lease policy.

## Dependency Injection

When your activities depend on services, there are two approaches:
Expand Down
Loading
Loading