Skip to content

Clarify workflow state isolation follow-up #189

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
rmcdaniel merged 1 commit into from
Oct 20, 2026
Merged

Clarify workflow state isolation follow-up #189

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions docs/portal/build/workflows-activities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,9 +67,10 @@ The released SDK shallow-clones attributed workflow handlers without rerunning
their constructors. Constructor-created nested objects and referenced
properties can remain shared across workflows and replay attempts. Do not use
them, injected services, static properties or captured shared objects for
execution-local mutable state. This handler-lifetime limitation remains open in
[#16](https://github.com/durable-workflow/sdk-php/issues/16); the proposed
fresh-construction correction is not released.
execution-local mutable state. The limitation is tracked in
[#16](https://github.com/durable-workflow/sdk-php/issues/16). The proposed
[fresh-construction correction](https://github.com/durable-workflow/sdk-php/pull/111)
is not released.

## Call a registered service

Expand Down
Loading