You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Let workflow code signal other workflows durably in every SDK #223
Workflow code in the service SDKs (Python, PHP SDK, Rust) cannot signal another workflow. The worker protocol's command set has no signal command, so the only path is an activity that calls the client. That adds an activity task and extra history per signal. Because activities run at least once and signal requests aren't deduplicated yet (.github#216), a retried activity also delivers the signal twice.
Embedded PHP can signal its own children through child handles (child workflows guide). But no runtime can durably signal an arbitrary workflow in the same namespace, and nothing documents this difference.
Acceptance criteria
Workflow code in Python, the PHP SDK, Rust and embedded PHP can signal another workflow in its namespace, by instance id or through a child handle. The signal is a workflow command recorded once in the sender's history, and replay never re-sends it.
The delivery outcome (accepted, or rejected as not found or closed) is recorded and visible to workflow code.
Tests in each runtime cover a successful signal, a closed or missing target, and cold replay of the sender.
The signals guide shows workflow-to-workflow signaling per SDK, and says when an activity is still needed, such as signal-with-start until .github#222.
Accepted as a product capability. A workflow command must durably record the sender's intent and the delivery outcome, and cold replay must return that recorded outcome without sending again. An activity that calls the client does not meet that contract.
Implementation follows the active safe-retry work in #216 and will reuse its canonical request identity, intent-conflict and retained-receipt rules. A worker command also needs a durable sender-outbox boundary so a crash between target admission and sender recording cannot duplicate delivery. Acceptance must cover that crash window, a missing/closed target, child and arbitrary same-namespace targets, namespace isolation and cold replay across embedded PHP and all three service SDKs. Signal-with-start remains #222.
General owns product/SDK/Core/PHP Server coordination. Native Server parity stays coordinated with server#325. This intake does not change frozen protocol actors or adopt a new native capability. The current entry-safety/security releases and #216 remain ahead of this implementation.
General open-item pass, November 4. Owner: Server and Workflow for retained sender/target contract; SDK owners for commands; General for product sequencing.
Next action: Resolve signal identity against216 and the durable sender-outbox crash boundary before adding portable same-namespace workflow signalling.
Action taken in this pass: Asked Server to map existing protocol/outbox ownership and missing decisions; signal-with-start remains222 and native frozen actors are not silently broadened.
General retains the cross-repository follow-through. Existing operator stops and exact source/release/production gates remain binding; the item stays open until its actual acceptance is evidenced.
Workflow: not started. Embedded needs a durable workflow-to-workflow signal command, recorded once with a sender outbox and reusing the #216 identity rules. Owner: workflow.
Decision (server#1251): signal_external_workflow lets a worker holding a workflow task signal any workflow in that task's namespace without the operator/admin role an HTTP signal needs; accepted as namespace-scoped, matching Temporal, and documented in the Server contract and reference.
Remaining after server#1251 and sdk-python#346 / sdk-php#438 / sdk-rust#294:
Embedded PHP (workflow repo): durable signal-external recorded once in the sender's history with a typed outcome (today a child-handle signal is sent directly and re-sent on replay).
Signals guide: per-SDK workflow-to-workflow signal examples (Python, PHP SDK, Rust, embedded PHP), in every docs locale with source hashes updated, including when an activity is still needed.
Status: the remaining two items each have an open PR. Both are green and waiting for independent review.
Embedded PHP:Let embedded workflow code signal other workflows durably (.github#223) workflow#1247 (head a1e12781). signalExternalWorkflow() / ChildWorkflowHandle::signalDurably() record ExternalSignalRequested plus one ExternalSignalDelivered/ExternalSignalFailed in the same transaction that admits the signal on the target. The key is workflow-signal:<run>:<seq>, and replay never re-sends. Outcomes, name rules and the request_id_reserved refusal match server#1251. Feature tests pass on MySQL, PostgreSQL and SQLite, and four replay fixtures were added. The API is experimental; the history events are frozen.
Embedded PHP:Let embedded workflow code signal other workflows durably (.github#223) workflow#1247 was redesigned after review as an outbox. The sender commits ExternalSignalRequested while holding only its own locks. Delivery then runs in the target's own transaction under the workflow-signal:<run>:<seq> key, and appends exactly one outcome to the sender, which resumes in a new workflow task. Transient database errors are retried and never fail the sender. A delayed sender task recovers a crash that happens between the commit and the delivery. The command is refused during cancellation cleanup, as on Server. The reviewer's concurrency scenarios are now tests that pass on MySQL and PostgreSQL. The PR is merged with main at f8cc3f00 and waiting for re-review.
Embedded PHP:Let embedded workflow code signal other workflows durably (.github#223) workflow#1247 shipped in Workflow 2.35.0 (release, tag commit 8d83a702, on Packagist; release verification passed). signalExternalWorkflow() / Workflow::signalExternalWorkflow() and ChildWorkflowHandle::signalDurably() record ExternalSignalRequested once, deliver through an outbox under workflow-signal:<run>:<seq>, and record one ExternalSignalDelivered/ExternalSignalFailed; replay never re-sends. Feature and cold-replay tests cover success, missing and closed targets, and replay. The API is experimental. Upgrade note: the workflow-signal: request-id prefix is now reserved (422 request_id_reserved).
Signals guide: #584 and #587 merged; durable-workflow.github.io#590 removes the pending-release note and names 2.35.0 as the first release, in all 7 locales. durable-workflow.github.io#589 records 2.35.0 as the stable Workflow release.
Server (server#1251), Python (sdk-python#346), PHP SDK (sdk-php#438) and Rust (sdk-rust#294) were already merged and released.
Remaining for this issue: nothing. Every acceptance criterion is met, so I'm closing it. Known limits, not acceptance gaps: the embedded API is experimental until a later minor release promotes it, and external PHP workers that use the Workflow package's worker-protocol runner replay recorded outcomes but refuse new signal-external commands (service-mode workers use the PHP SDK's command).
Activity
rmcdaniel commentedon Oct 20, 2026
Accepted as a product capability. A workflow command must durably record the sender's intent and the delivery outcome, and cold replay must return that recorded outcome without sending again. An activity that calls the client does not meet that contract.
Implementation follows the active safe-retry work in #216 and will reuse its canonical request identity, intent-conflict and retained-receipt rules. A worker command also needs a durable sender-outbox boundary so a crash between target admission and sender recording cannot duplicate delivery. Acceptance must cover that crash window, a missing/closed target, child and arbitrary same-namespace targets, namespace isolation and cold replay across embedded PHP and all three service SDKs. Signal-with-start remains #222.
General owns product/SDK/Core/PHP Server coordination. Native Server parity stays coordinated with server#325. This intake does not change frozen protocol actors or adopt a new native capability. The current entry-safety/security releases and #216 remain ahead of this implementation.
rmcdaniel commentedon Nov 4, 2026
General open-item pass, November 4. Owner: Server and Workflow for retained sender/target contract; SDK owners for commands; General for product sequencing.
Next action: Resolve signal identity against216 and the durable sender-outbox crash boundary before adding portable same-namespace workflow signalling.
Action taken in this pass: Asked Server to map existing protocol/outbox ownership and missing decisions; signal-with-start remains222 and native frozen actors are not silently broadened.
General retains the cross-repository follow-through. Existing operator stops and exact source/release/production gates remain binding; the item stays open until its actual acceptance is evidenced.
rmcdaniel commentedon Nov 11, 2026
Workflow: not started. Embedded needs a durable workflow-to-workflow signal command, recorded once with a sender outbox and reusing the #216 identity rules. Owner: workflow.
rmcdaniel commentedon Nov 11, 2026
Server: remaining, tracked in durable-workflow/server#1134. Next: implement the signal-external worker command after server#934. Owner: server.
rmcdaniel commentedon Nov 11, 2026
PHP: waits on the signal-external worker command (server#1134). Owner: server, then sdk-php.
Add native-recorded evidence and the 191-character signal name limit
Check that commands after two signals take the next sequences
rmcdaniel commentedon Nov 19, 2026
Decision (server#1251):
signal_external_workflowlets a worker holding a workflow task signal any workflow in that task's namespace without the operator/admin role an HTTP signal needs; accepted as namespace-scoped, matching Temporal, and documented in the Server contract and reference.rmcdaniel commentedon Nov 19, 2026
Remaining after server#1251 and sdk-python#346 / sdk-php#438 / sdk-rust#294:
Refuse signal names the Server would refuse, in workflow code
rmcdaniel commentedon Nov 19, 2026
Status: the remaining two items each have an open PR. Both are green and waiting for independent review.
a1e12781).signalExternalWorkflow()/ChildWorkflowHandle::signalDurably()recordExternalSignalRequestedplus oneExternalSignalDelivered/ExternalSignalFailedin the same transaction that admits the signal on the target. The key isworkflow-signal:<run>:<seq>, and replay never re-sends. Outcomes, name rules and therequest_id_reservedrefusal match server#1251. Feature tests pass on MySQL, PostgreSQL and SQLite, and four replay fixtures were added. The API is experimental; the history events are frozen.This stays open until both merge and the embedded change ships in a release.
🤖 Generated with Claude Code
rmcdaniel commentedon Nov 20, 2026
Update:
ExternalSignalRequestedwhile holding only its own locks. Delivery then runs in the target's own transaction under theworkflow-signal:<run>:<seq>key, and appends exactly one outcome to the sender, which resumes in a new workflow task. Transient database errors are retried and never fail the sender. A delayed sender task recovers a crash that happens between the commit and the delivery. The command is refused during cancellation cleanup, as on Server. The reviewer's concurrency scenarios are now tests that pass on MySQL and PostgreSQL. The PR is merged with main atf8cc3f00and waiting for re-review.🤖 Generated with Claude Code
rmcdaniel commentedon Nov 20, 2026
Embedded PHP is done and released.
8d83a702, on Packagist; release verification passed).signalExternalWorkflow()/Workflow::signalExternalWorkflow()andChildWorkflowHandle::signalDurably()recordExternalSignalRequestedonce, deliver through an outbox underworkflow-signal:<run>:<seq>, and record oneExternalSignalDelivered/ExternalSignalFailed; replay never re-sends. Feature and cold-replay tests cover success, missing and closed targets, and replay. The API is experimental. Upgrade note: theworkflow-signal:request-id prefix is now reserved (422request_id_reserved).Server (server#1251), Python (sdk-python#346), PHP SDK (sdk-php#438) and Rust (sdk-rust#294) were already merged and released.
Remaining for this issue: nothing. Every acceptance criterion is met, so I'm closing it. Known limits, not acceptance gaps: the embedded API is experimental until a later minor release promotes it, and external PHP workers that use the Workflow package's worker-protocol runner replay recorded outcomes but refuse new signal-external commands (service-mode workers use the PHP SDK's command).
🤖 Generated with Claude Code