PHP SDK 3.12.0

PHP SDK 3.12.0 adds opt-in activity continuations for Native Server 3.4.0.

Pass enableActivityContinuation: true to the Worker constructor to turn it on; it defaults to false, so existing workers behave exactly as before. When the Server advertises activity_workflow_continuation, an opted-in worker replays the run's bounded history together with its successful activity result and submits the next eligible workflow commands with the same completion. Native Server 3.4.0 commits the result and the commands in one transaction.

The fast path covers sequential remote activities, timers, workflow completion and version markers. Local activities, parallel groups, selections, cancellation scopes, message waits and update or cancellation state keep the ordinary completion path, as do older Servers, Server declines and workflow code that reads business time at or after the speculative result. Errors and uncertain completion outcomes use the existing recovery rules.

Before introducing older Server nodes or downgrading the Server, drain or disable opted-in workers. See the worker guide.

PHP ^8.1, worker protocol 1.20 and control plane 2 are unchanged. No throughput or latency improvement is claimed yet; installed qualification against the published Server 3.4.0 is tracked in #341.

Update — fixed in PHP SDK 3.12.1

The continuation slowdown noted at release time was in the PHP SDK, not the Server. PHP SDK 3.12.1 fixes it: an installed test of Server 3.4.0 + SDK 3.12.1 shows 120/120 continuations accepted and the same latency as the ordinary path (median 562 ms vs 563 ms for a 3-activity workflow). If you enable continuations, use SDK 3.12.1 or later.