NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #1992 most downloaded on Packagist
Embedded durable workflow runtime and orchestration engine for Laravel applications.
Latest stable
2.22.0
Last release 12 days ago
08 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
623 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Recover signal, signal-with-start, cancellation and termination commands when MySQL rolls back their owned root transaction after a concurrency confli
Recover signal, signal-with-start, cancellation and termination commands when MySQL rolls back their owned root transaction after a concurrency conflict. Retries use the existing workflows.storage.transaction_attempts limit.
Successful retry preserves the original runs, histories and deadlines and records each accepted command once. Caller-owned transactions and unrelated database failures keep their original behavior. SQLite writer admission and PostgreSQL policies are unchanged. This does not add SDK HTTP retries or repeat user activities.
Restart long-running application and worker processes after upgrading. A pinned Server image needs its own dependency update; installing this library elsewhere does not change that image.
This compatible patch starts from published 2.5.27. It includes only the focused runtime correction, eight real MySQL regression controls, release notes and exact version metadata. No dependency, schema or draft tracing/Nexus change is included.
The source candidate and independent compatible release candidate pass their database shards, supported Laravel/PHP source upgrades, corpus, quality, unit and coverage gates. Source Sonar passes with zero unresolved PR findings.
Published verification passes all 17 registry/platform and supported Laravel/PHP upgrade jobs. Normal Composer installation on PHP 8.3.35 / Laravel 13.37.0 / MySQL 8.4.5 passes all eight real concurrency controls and 180 assertions. Updating only this package changes the published 2.5.27 baseline's four actual deadlock failures to passes, while preserving all four negative controls. The loaded vendor class matches the exact released source and all other dependency objects remain unchanged.
See #819, source #820 and compatible release #821. The original mixed-load failure remains failed; SDK hosting and affected Server acceptance remain separate.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Keep a completed activity callback's result in memory while SQLite admits its publication, within the original task lease and earliest activity deadli
Keep a completed activity callback's result in memory while SQLite admits its publication, within the original task lease and earliest activity deadline. Capture that bound once with a monotonic clock and recheck the stored task and attempt before publication.
Only a proven root rollback before publication starts can retry. The callback and an entered publication body do not repeat. Expired or replaced claims, uncertain commits, failed rollback acknowledgments and exhausted budgets retain their original refusal behavior. Other mutation and admission limits are unchanged.
Restart long-running queue workers after upgrading. This compatible patch starts from 2.5.26 and includes the focused #816 correction, regression controls and release metadata. It does not include the draft tracing or other development features.
Source PR, full source candidate, fresh main 38912375676 and compatible full candidate 38910103083 pass, including database shards, supported source upgrades, corpus, quality and coverage. The original Sonar complexity finding is fixed; the exact source gate passes.
Published verification 38915513763 passes all 17 registry/platform and supported Laravel/PHP upgrade jobs. A normal Composer installation on PHP 8.5.11 / Laravel 13.37 passes 78 focused controls / 895 assertions, including actual competing-writer publication and stale-claim refusal.
The fresh continuous-worker consumer completes all 64 activities once, the original workflow and exact typed output/history/policy/deadline checks within its original 90-second observer. It records three repairs, so the separate strict zero-repair metric remains failed. Installed outcome. The Sample update is delivered, including both native installed-image qualifications. Earlier cutoff and observer failures remain failed; #809 retains the remaining acceptance and hosted follow-through. This release does not promise contention-free SQLite operation or qualify the draft tracing fan-out.
Retry a proven rolled-back SQLite acknowledgment delete within the existing bounded retry cutoff, using capped cooperative backoff. The delete remains
Retry a proven rolled-back SQLite acknowledgment delete within the existing bounded retry cutoff, using capped cooperative backoff. The delete remains fenced to the original job, queue, reservation timestamp and attempt count. A newer reservation survives, and the handler is not rerun to acknowledge a delivery.
Uncertain commits, failed rollback acknowledgments, changed connections, constraint errors and exhausted retry budgets still propagate their original failures. Workflow policies, logical attempts and deadlines are unchanged. Restart long-running workers after upgrading.
This compatible patch starts from published 2.5.25 and includes only the acknowledgment correction from #814, its focused controls and release metadata. Exact source and compatible full CI, database shards, supported source upgrades, corpus, quality and coverage pass. The source Sonar gate passes with zero unresolved PR findings.
Published-package verification and all 16 supported Laravel/PHP upgrade profiles pass in 38907488268. A normal Composer installation on Laravel 13.37 passes 44 acknowledgment and embedded execution controls / 718 assertions. Sample's separately pinned image update is tracked in durable-workflow/sample-app#231.
Issue #809 remains open for the separately reproduced claim/outcome pressure. This release does not promise contention-free SQLite operation; the unpublished outcome-admission correction in #816 is separate.
This patch allows more confirmed, rolled-back SQLite write-admission attempts within the existing retry window, before a task's claim or execution bod
This patch allows more confirmed, rolled-back SQLite write-admission attempts within the existing retry window, before a task's claim or execution body starts. It preserves explicit attempt limits, ordinary mutation retries and uncertain commit/rollback handling. Activity callbacks are not repeated to publish their results. Native contention still propagates when admission retries are exhausted.
The exact source and compatible release candidate passed their full CI matrices. Registry/platform verification and all 16 supported published Laravel/PHP upgrade profiles pass. The first normally installed 64-activity/four-worker profile also passes with exact output, original history/deadlines, callbacks once and zero failed deliveries or repairs. Consumer outcomes and limits are recorded on #809. Sample's lock/image follow-through remains pending in Sample #230.
The first zero-repair installed pass above used Laravel 13.30.1. A separate Laravel 13.37.0 original completes all 64 activities once, with exact original output/history/deadlines and no failed deliveries, but uses one repair. Its strict zero-repair metric remains failed. Consumer outcomes and remaining queue-only qualification are tracked in #809.
The earlier 2.5.24 fan-out original remains a failed clean stress result: all 64 activities completed once, with one failed pre-claim transport delivery and one repair. Separate source observations are recorded on #812. This release does not claim contention-free operation. Issue #809 remains open.
Changes: #812 and #813.
Improves embedded database-queue recovery during concurrent fan-out.
Improves embedded database-queue recovery during concurrent fan-out.
Apply package migrations and restart queue workers after upgrading. The new nullable delivery reference is internal metadata. Legacy rows and unsupported queue transports retain the existing recovery path.
This compatible patch starts from 2.5.23 and includes the focused correction from #810. It does not include unrelated development changes.
Qualification note: the first normal-installed four-worker SQLite fan-out completed all 64 activities correctly but required one repair after a pre-claim delivery failure. Clean stress acceptance remains open in #809. This release does not claim contention-free fan-out. Published upgrade verification tracks the supported Laravel/PHP profiles.
Embedded local-activity retries now publish their existing follow-up Laravel queue job after the execution transaction commits. The retry keeps its or
Embedded local-activity retries now publish their existing follow-up Laravel queue job after the execution transaction commits. The retry keeps its original task, policy, backoff and deadlines.
Regression coverage includes immediate and delayed retries, exhausted policy, normal success, poll mode, transaction rollback and cold replay. A watchdog concurrency test now compares stored database snapshots and deliberately covers PostgreSQL timestamps with trailing fractional zeros.
No schema migration is needed.
For an already affected waiting run, upgrade and use the normal Repair action once its retry task is overdue. Repair retains the original deadline.
Published-package verification passes all16 declared Laravel/PHP upgrades. A clean Composer installation passes the six queue/rollback controls and an upgrade recovery of the same original run. The Sample App published image also passes both native architecture startup checks. Qualification and consumer delivery.
Fixes #805. Source: #806 and #808. Compatible release: #807.
Fix typed workflow-task discovery for the valid workflow type "0".
Fix typed workflow-task discovery for the valid workflow type "0".
The discovery filter now preserves every nonempty string. "0", "17" and "017" remain distinct. Namespace, queue, connection, build and availability checks are unchanged.
This compatible patch is based on 2.5.21. Source and regressions: #800. Stable backport: #801. Full stable qualification: 38708551385.
Server images pin their Workflow dependency. Server 2.8.3 still contains Workflow 2.5.21; the corrected image and installed-consumer follow-through are tracked in #799.
Fixes a worker/watchdog row-lock deadlock during task recovery.
Fixes a worker/watchdog row-lock deadlock during task recovery.
Compatible patch from 2.5.20. Source: #797. Stable backport: #798. Full exact candidate qualification: https://github.com/durable-workflow/workflow/actions/runs/38670181729.
Reduces database-cache writes from idle queue polling.
Reduces database-cache writes from idle queue polling.
This patch changes watchdog cache coordination. Workflow history, task authority and execution contracts are unchanged. It contains no pending Nexus or tracing capability.
Source: #793. Stable patch: #795. Exact merged qualification: https://github.com/durable-workflow/workflow/actions/runs/38589264995.
This patch prevents concurrent SQLite writes from failing V2 workflow and activity task claims, or activity result publication.
This patch prevents concurrent SQLite writes from failing V2 workflow and activity task claims, or activity result publication.
There are no schema changes. Update the package and gracefully restart long-lived workers to load the correction.
composer require durable-workflow/workflow:^2.5.19
Details: https://github.com/durable-workflow/workflow/issues/783
Fix SQLite contention in embedded V2 workflow starts, signals and task handling.
Fix SQLite contention in embedded V2 workflow starts, signals and task handling.
Use the configured Workflow storage database when it differs from the application database.
Safe mutation retries require proof that the original root transaction rolled back. Workflow execution acquires SQLite's write lock before reading durable state or entering application code. Activity result recording retries independently of the activity callback, preserving original attempts and deadlines. Nested transactions and uncertain commit or rollback acknowledgements keep their original errors.
The correction supports the existing Laravel 9–13 range. Other database transaction behavior remains unchanged.
Fix SQLite database queue acknowledgement after a workflow job's handler returns.
Fix SQLite database queue acknowledgement after a workflow job's handler returns.
This extends the default SQLite database queue integration across supported Laravel 9 through 13 while retaining their existing reservation behavior. Restart queue workers after upgrading.
The correction and actual two-worker timer qualification are tracked in #772. SQLite queue recovery guidance explains reservation versus acknowledgement errors and safe recovery from sustained contention.
Embedded replay now rejects changes to explicitly authored activity retry policies before consuming an original result or scheduling new work. It comp
Embedded replay now rejects changes to explicitly authored activity retry policies before consuming an original result or scheduling new work. It compares complete stored backoff lists, including unused entries, and preserves the original run/task for matching-code repair.
The check covers direct, grouped, selected and query replay. Activity class defaults and supported legacy histories without a recorded policy retain their existing behavior.
The isolated backport starts from published 2.5.15. Reviewed candidate and fresh merged source qualification pass, including database shards, Laravel/PHP upgrade profiles, counterfactual regression corpus, quality and coverage. Published-package verification and normally installed original-run repair qualification follow this release.
Relevant issue: #744. This release excludes main's pending Nexus work and does not establish native Server or Cloud adoption.
Preserve unclaimed SQLite database-queue jobs after a reservation write is refused and the original transaction has fully rolled back. The worker repo
Preserve unclaimed SQLite database-queue jobs after a reservation write is refused and the original transaction has fully rolled back. The worker reports the error and selects work again, without failing the workflow before its handler runs.
The package installs this guard for the default database connector on affected Laravel 12/13 versions. Custom queue managers/connectors, other databases, invalid jobs and uncertain transaction outcomes retain their existing behavior.
Restart queue workers after upgrading. Already failed workflows are not automatically restarted. No database migration is required.
Qualified from the published 2.5.14 base, with pending main/Nexus changes excluded. Full source and exact merged-source database, Laravel 9–13, corpus, quality and coverage checks pass. Published package verification follows through the release workflow.
Related: #772. Implementation: #775.
Activity completion, failure and heartbeat renewal now respect the current lease and execution deadlines. Expired authority cannot be revived by a lat
Activity completion, failure and heartbeat renewal now respect the current lease and execution deadlines. Expired authority cannot be revived by a late heartbeat or outcome. The guard checks again after payload preparation.
Valid renewal, internal timeout handling and normal recovery of the same activity execution remain supported. The correction applies to embedded Laravel execution and the PHP Server package.
Based on published 2.5.13, with only this correction, focused tests, documentation and exact release metadata. Full source qualification passed all database feature shards, coverage and Laravel 9–13 upgrade profiles on the identical reviewed release tree.
PHP Server image and installed consumer follow-through are tracked in Workflow #769.
Valid historical duplicates keep their positions and clocks, and compatible patch, version and deprecation helpers retain the same numeric decision wi…
Workflow 2.5.13 rejects malformed canonical version-marker bounds before replay consumes or skips a retained marker. Missing or non-integer bounds, inverted ranges and a recorded version outside its recorded bounds fail explicitly. Valid historical duplicates keep their positions and clocks, and compatible patch, version and deprecation helpers retain the same numeric decision with their own result projections.
This compatible correction is based on published 2.5.12. The production change is limited to VersionResolver and VersionDecisions, with unchanged marker and command wire shapes. It excludes later main/Nexus work. Existing retained histories and shared fixture cohorts remain unchanged.
Source qualification: PR #768, full stable run 38335116238, 3,862 unit tests / 49,805 assertions, v2 line coverage 93.49%, all MySQL/PostgreSQL/MariaDB and Laravel 9–13 source profiles passed. The committed conformance mirror matches public suite 47 and its pinned protocol resolver digests. Main correction #767 and contract #744 provide the implementation and agreed semantics.
Published-package verification and affected consumer rollout receipts are tracked in #744. A new library tag does not update pinned Server images or native/shared qualification. Broader #744 coverage and #747/#748 remain separate work.
Service calls now retain their original deadline from admission through retries and duplicate requests. Repair expires an overdue call without API pol
Service calls now retain their original deadline from admission through retries and duplicate requests. Repair expires an overdue call without API polling, and a late service result cannot replace its timed-out outcome or deliver a second caller result.
Deadline policies accept either a positive integer timeout_seconds or an explicit-offset RFC3339 deadline_at with up to six fractional digits. Call views retain UTC microsecond acceptance and deadline timestamps.
Before upgrading, back up the database and replace old application and worker processes. The migration derives existing deadlines from original acceptance and policy. Unsupported stored policies stop migration with the affected call ID.
Full source qualification passes unit/coverage, all MySQL/PostgreSQL shards, MariaDB, five Laravel upgrade checks, quality and the official embedded replay corpus. Published package and downstream Server image verification are recorded on #761.
Linked workflow completion, failure and cancellation now close the original durable service call.
Install with composer require durable-workflow/workflow:2.5.11. Standalone Server deployments need an image that includes this package.
Published cross-SDK qualification is tracked in Workflow #753.
Fix manual repair when a workflow is replay blocked and an older activity is still pending. Repair now redispatches the blocked workflow task first, p
Fix manual repair when a workflow is replay blocked and an older activity is still pending. Repair now redispatches the blocked workflow task first, preserving the activity and original history. With compatible workflow code restored, the repaired task can wait for that original activity and the same run can finish after one activity execution.
Includes the executable cold-replay and pending-activity repair regression from #756. Ordinary activity recovery and automatic exclusions for replay-blocked runs retain their existing behavior.
Standalone Server users need an image that includes this Workflow dependency; updating a separate Composer installation does not change a pinned Server image. Published image qualification is tracked in durable-workflow/server#397 and #755.
Default queue workers now include durable tasks that inherit the application's default connection when scanning for overdue work, missing resume tasks
Default queue workers now include durable tasks that inherit the application's default connection when scanning for overdue work, missing resume tasks and deadlines. Previously, a worker using a resolved name such as redis could skip a task whose stored connection was implicit.
Other connections and queues remain isolated. Existing API and lease defaults are preserved.
Source qualification and published-package verification are recorded in Workflow #751.
Incompatible recorded workflow versions now block embedded replay while preserving the original run, history and completed work. Restore a compatible
Incompatible recorded workflow versions now block embedded replay while preserving the original run, history and completed work. Restore a compatible workflow definition, then explicitly repair the run to continue with a new fenced attempt without repeating completed activities.
The exception remains catchable as VersionNotSupportedException; ordinary application exceptions keep their existing behavior. Version-marker payloads and SDK wire contracts are unchanged. Runs already closed by older versions remain closed.
Source repair and release preparation: #749, #750. Qualification and affected consumer updates are tracked in #744. Exact published-package verification follows this tag; pinned Server images require a rebuilt release to receive the library fix.
Reuse a workflow's first patch or version decision for repeated calls without recording duplicate markers. Continue validating each call's supported r
Reuse a workflow's first patch or version decision for repeated calls without recording duplicate markers. Continue validating each call's supported range.
Cold replay preserves duplicate markers retained by older releases, including their original command positions and recorded clock values. Executor, query reconstruction and fiber replay share this behavior.
Verified through the full database and Laravel matrices, coverage and 53 replay corpus fixtures, including fail-before/pass-after compatibility cases. All 17 published-package checks pass. A fresh Composer installation resumes a real old 2.5.6 run in a separate cold process, preserving its complete history prefix, both recorded clocks, two legacy markers, original activity sequence and one completion. A fresh 2.5.7 run records one marker across repeated calls.
Upgrade every workflow executor, query replayer and fiber host that can read the same runs before resuming processing. Keep older builds isolated from new histories. A 2.5.6 worker cannot replay a fresh 2.5.7 history containing repeated calls to one patch ID because it expects an additional marker. It reports history_shape_mismatch. Do not downgrade readers of those histories. Existing duplicate-marker histories remain readable in 2.5.7.
The published Server 2.5.16 image still embeds Workflow 2.5.6. Updating this Composer package does not update that image.
Related: #744, #745 and #746.
Fix scheduled work being skipped after transient SQLite contention.
Fix scheduled work being skipped after transient SQLite contention.
Due ticks, buffered admissions and backfills now retain the original occurrence, history and remaining action budget after SQLite BUSY or LOCKED errors. The evaluator reports the failed attempt and the next ordinary attempt can admit the original occurrence once. Permanent errors keep their existing accounting.
No API or schema change is required. Embedded Laravel applications receive the fix through a normal Composer update. Self-hosted Server installations receive it in the following Server image release.
Fix complete cancellation and termination diagnostics when a reason contains a literal NUL. Terminal history and the failure row now store the same lo
Fix complete cancellation and termination diagnostics when a reason contains a literal NUL. Terminal history and the failure row now store the same lossless JSON string literal on every supported database. The original reason remains unchanged in Avro command and history payloads.
Ordinary messages and SDK cancellation outcomes retain their behavior. No schema migration is required.
Fix: https://github.com/durable-workflow/workflow/pull/742
The issue tracks the pinned Server image update and published consumer verification: https://github.com/durable-workflow/workflow/issues/741
Preserve the authored signal wait identity and workflow sequence when a buffered signal is delivered. A cold replay consumes the same wait, while orig
No SDK or wire schema change is required. See PR 712 and issue 711.
Full source qualification passes quality checks, MySQL/PostgreSQL/MariaDB, supported Laravel upgrades, the regression corpus and the complete-source coverage gate at 91.92%. Source c39025af47e0307103e48d98ead71067ff243ef6 has the same tree as the qualified PR head. The new frozen replay fixture also fails against the original source.
Published package verification and pinned Server/consumer follow-through remain on issue 711.
Correct hourly dashboard throughput outside UTC. Projection timestamps use a UTC elapsed-hour cutoff, while legacy rows use the application's timestam
The worker protocol and public method signatures are unchanged.
Full source qualification passes the database and Laravel matrix, quality checks, regression corpus and coverage gate. The merged source tree is identical to the qualified tree. Focused PostgreSQL dashboard coverage passes 37 cases with 147 assertions, including offset zones, daylight-saving boundaries, legacy timestamps, read-only observation and writer cleanup.
See PR #649 for implementation and published consumer verification.
Fix native workflow queries while waiting for multiple child workflows.
Fix native workflow queries while waiting for multiple child workflows.
Query replay now waits for the child's outcome to be committed to the parent history before advancing an all() wait. Completed, failed, cancelled and terminated child rows cannot prematurely resolve the parent's query state.
Regression coverage checks committed outcomes, mixed waits and repeated queries that leave durable history unchanged. Execution and portable SDK contracts are unchanged.
See #645.
Fix offline replay and queries for legacy PHP workflows that take the default version branch when an activity or timer already occupies that history p
Fix offline replay and queries for legacy PHP workflows that take the default version branch when an activity or timer already occupies that history position.
Replay now resolves the version before checking the marker shape, matching live execution. Malformed markers and genuine activity or timer drift remain rejected.
Regression coverage includes pending and completed legacy histories, cold worker replay and repeated queries without changing durable history.
See #643.
PHP schedules can now set workflow execution and run timeouts through the supported ScheduleManager API.
PHP schedules can now set workflow execution and run timeouts through the supported ScheduleManager API.
Pass executionTimeoutSeconds and runTimeoutSeconds to create(), or set the corresponding action fields in createFromSpec(). Manual triggers and automatic starts forward the same budgets. Updating a schedule changes future starts while preserving deadlines for runs already started. Omitted timeouts retain existing behavior, and PHP timeout values follow StartOptions validation.
The schedule guide includes runnable examples and explains execution versus run budgets. No database migration or worker protocol change is required.
Details: https://github.com/durable-workflow/workflow/issues/627
Fixes an unnecessary task-to-run database lookup when compatibility resolution receives an explicit run with a null marker. The supplied run remains a
Fixes an unnecessary task-to-run database lookup when compatibility resolution receives an explicit run with a null marker. The supplied run remains authoritative, which also avoids a Laravel lazy-loading violation in that path.
Task-marker precedence and the relationship fallback when no run is supplied are preserved. No schema or worker protocol changes are required.
Thanks to @vanducng for the report, fix and regression tests.
Details: https://github.com/durable-workflow/workflow/issues/636
Add bounded reads for operator run views.
Add bounded reads for operator run views.
These optional observer methods preserve custom observer compatibility. Worker execution and portable protocol behavior are unchanged.
Full merged-source checks pass on baf795cea9bd6f582e001794bd72577f015dd1f2,
including coverage, MySQL, PostgreSQL, MariaDB and Laravel 9–13 upgrades.
A fresh registry install passes all 37 bounded-reader cases / 253 assertions.
The published registry/platform checks and all supported Laravel 9–13 / PHP
upgrade cells pass in release verification.
See #633, #634 and #635. Supporting Waterline and Server delivery continues in durable-workflow/waterline#141.
Improve bounded operator dashboards.
Improve bounded operator dashboards.
Worker execution and protocol behavior are unchanged. Full source checks pass on the release commit, including coverage, MySQL, PostgreSQL, MariaDB and the Laravel 9–13 upgrade matrix.
See #630, #631 and #632. Supporting Server and Waterline delivery continues in durable-workflow/waterline#141.
Dashboard trends now aggregate completed and failed counts in the database, and median duration selects the middle value without loading every duratio
Dashboard trends now aggregate completed and failed counts in the database, and median duration selects the middle value without loading every duration.
Adds an opt-in boundedDashboardSummary() observer method that defers complete
history audits. Unevaluated audit counts are null with
history_audit_evaluation: not_requested. Existing dashboard and metrics APIs
retain their full audits.
Qualified on SQLite, MySQL, PostgreSQL and MariaDB, with supported Laravel upgrade checks and the complete unit and coverage gates passing. Source checks.
Waterline adoption is in Waterline #142, with the standalone Server endpoint in Server #305. Workflow execution and portable worker protocols are unchanged.
Correct configured execution namespaces and queued PHP workflow recovery.
Correct configured execution namespaces and queued PHP workflow recovery.
Workflow\V2\WorkflowStub::make() persists the configured namespace on new
instances, runs and tasks, matching the control-plane start API. PHP schedules
start in their schedule's namespace, including an explicit override.
An existing instance cannot be reassigned to a different namespace by a new start. Load existing instances in their original namespace. This release does not migrate older unscoped instances.
Addresses #607, #617 and #620. No portable protocol change or SDK upgrade is required. Server images need an updated embedded Workflow package.
Preserves worker-session routing in activity history so cold replay can validate the original session identity, requirements and lifetime options. Ord
Preserves worker-session routing in activity history so cold replay can validate the original session identity, requirements and lifetime options. Ordinary activity histories retain their previous field shape.
Upgrade the standalone Server image to consume this fix. Existing stored histories are preserved. The patch does not reconstruct session metadata that earlier releases omitted.
Native 2.4.0 adds whole-run cooperative cancellation with an immutable request context, original deadline and one bounded parent/child/Activity tree.
Native 2.4.0 adds whole-run cooperative cancellation with an immutable request context, original deadline and one bounded parent/child/Activity tree. Workflow code can perform shielded durable cleanup, inspect its remaining budget and resume at the same delivery boundary after worker replacement.
Operation policies distinguish trying cancellation, waiting for cancellation completion and abandoning eligible work. Managed stop receipts fence stale Activity results. The canonical cascade records delivery, stop evidence, cleanup recovery and terminal outcomes.
Scheduler lease repair and cancellation-deadline enforcement now acquire the run before its tasks, matching operator repair and Server mutations. The PHP 8.1 minimum remains supported.
The published stable mixed PHP parent, Python child, Rust remote Activity and PHP local Activity demonstration passes 236 assertions. Both runs finish Cancelled with cleanup completed 15.802418 seconds after the original request, before its unchanged 30-second deadline. It includes physical stop without application heartbeats, actual cleanup-worker SIGKILL, replacement replay, stale result refusal, duplicate identity/deadline and one API/CLI view. The unchanged published Waterline frontend displays the qualified cascade on desktop and mobile.
The demonstration uses published Native 2.4.0 in Server 2.5.0, PHP SDK 2.2.0, Python 2.4.0, Rust 3.0.0 and CLI 2.2.0. Waterline 2.1.0 is also published. Published lifecycle conformance passes all 12 cells. Independently cancellable scopes remain disabled experimental source preview outside the stable release claim. Existing immediate cancellation remains available through its legacy API.
Exact tuples and comparison results are recorded in shared cancellation #136.
Scheduler repair now acquires a workflow run before its task, matching operator repair and Server mutations. The task's run association is rechecked u
The concurrency regression runs actual repair and watchdog passes on MySQL and PostgreSQL. Both databases pass the expired-lease and expired-cancellation-deadline cases. Both MySQL cases fail with the original watchdog implementation.
Complete database, framework upgrade, code quality, unit coverage and regression corpus qualification passes at https://github.com/durable-workflow/workflow/actions/runs/37425470512.
This is a prerelease for the whole-run cooperative cancellation contract. General independently cancellable scopes remain a disabled source preview. Published mixed-language acceptance remains tracked in https://github.com/durable-workflow/.github/issues/136.
feat: strengthen canonical cancellation context and propagation by @rmcdaniel in https://github.com/durable-workflow/workflow/pull/603
Full Changelog: https://github.com/durable-workflow/workflow/compare/2.3.5...2.4.0-rc.1
Fixes an infinite queue-release loop after a legacy workflow continues as new. Signal and Timer jobs belonging to a continued run now retire instead o
Fixes an infinite queue-release loop after a legacy workflow continues as new. Signal and Timer jobs belonging to a continued run now retire instead of following the running successor and repeatedly retrying the old operation. Jobs for the current running workflow retain their normal retry behavior.
The regression covers two- and three-run chains with pending signals and timers. Full main CI, database shards, embedded Laravel upgrade checks and coverage gates pass on the release commit. The portable V2 contract is unchanged.
Install with composer require durable-workflow/workflow:2.3.5.
Fix: #607. Implementation: #608.
Repairs now preserve the original run's namespace when recreating workflow, activity and timer tasks. This keeps recovered work discoverable by Server
Repairs now preserve the original run's namespace when recreating workflow, activity and timer tasks. This keeps recovered work discoverable by Server workers polling that namespace.
The repair pass also restores a missing namespace on existing tasks when they are eligible for redispatch, expired lease recovery or replay recovery. Existing namespace assignments and current leases are preserved. No database migration or SDK protocol change is required.
Cooperative cleanup deadlines now close runs on the runtime's next repair pass even when no compatible workflow worker is available.
Cooperative cleanup deadlines now close runs on the runtime's next repair pass even when no compatible workflow worker is available.
cancellation_deadlines_enforced in repair-pass JSON.Ordinary Worker protocol remains 1.19. Service-mode cooperative cancellation is still undergoing separate model and SDK qualification.
Details: Workflow #604.
Fix condition waits inside parallel groups and keyed selections after an insufficient signal.
Fix condition waits inside parallel groups and keyed selections after an insufficient signal.
Ordinary Worker protocol remains 1.19. Rust service Workers should use SDK 2.1.3 for replay of grouped condition reopens.
Source qualification includes the full database and Laravel matrix, durable replay corpus, and five actual Worker scenarios with a fresh process per claim. Stable Server publication and exact published consumer follow-through are tracked in issue 601.
Recover an expired workflow task even when an older activity remains legitimately in flight. A replacement worker can claim the workflow task's next a
Recover an expired workflow task even when an older activity remains legitimately in flight. A replacement worker can claim the workflow task's next attempt without waiting for the activity's separate lease. The active activity's ownership, attempt, lease and history are preserved.
Public APIs, database schema and worker protocol defaults are unchanged.
The full source matrix passes supported database, embedded Laravel, quality, corpus and coverage gates. The published-package verification passes package identity, portable platform contracts and all 16 supported Laravel/PHP upgrade combinations.
Immutable source: fb3f3e59a4342fdebf8ced6160798906c3ee4387.
The self-hosted image update is being qualified in Server PR #292. Issue #599 remains open through published Server and affected-consumer verification. The attached counterfactual JUnit files document the source regression and Python candidate reproduction. They are separate from the published-package results above.
Add an optional cooperative workflow-task bridge for service adapters. Delivery persists the original request and authored call boundary while preserv
Add an optional cooperative workflow-task bridge for service adapters. Delivery persists the original request and authored call boundary while preserving the workflow lease for bounded cleanup.
Parallel delivery reserves the full durable sequence range. Selection handles identify their previously opened operation. Retries reuse the persisted marker, interrupted work is fenced, and terminal cleanup retains the original cancellation outcome.
Existing custom workflow-task bridges remain compatible. Worker protocol 1.19 is unchanged. The service request, observation and worker capability integration continues in durable-workflow/.github#136.
Implementation and qualification: https://github.com/durable-workflow/workflow/pull/598
Fix portable cleanup command sequencing after cooperative cancellation delivery. The interrupted durable call now retains its position even when it ha
Fix portable cleanup command sequencing after cooperative cancellation delivery. The interrupted durable call now retains its position even when it had not opened an activity or wait, so subsequent cleanup uses the next sequence.
Includes retained cold-replay and database-backed bridge regression coverage. Existing terminal service cancellation behavior is unchanged. The separate cooperative service request remains tracked in durable-workflow/.github#136.
Implementation and qualification: https://github.com/durable-workflow/workflow/pull/597
Portable workflow tasks now enforce the persisted cooperative cancellation cleanup deadline before lease renewal and command acceptance. At expiry, th
Portable workflow tasks now enforce the persisted cooperative cancellation cleanup deadline before lease renewal and command acceptance. At expiry, the engine cancels the original run, revokes open work and preserves one terminal cancellation linked to the original request.
Valid cleanup before the deadline and existing ordinary timeout behavior are preserved. The stable service /cancel operation remains terminal. This patch does not introduce a service cooperative request operation or advertise SDK cleanup support.
Qualified with the full source database, unit coverage, replay corpus and Laravel upgrade matrix. Published package verification runs on this exact tag. Server's pinned-image delivery is tracked separately in Server #286.
Fix and evidence: Workflow #595.
Workflow 2.2.21 reduces the projection work performed when ordinary sequential activities complete or finally fail in long-running workflows.
Workflow 2.2.21 reduces the projection work performed when ordinary sequential activities complete or finally fail in long-running workflows.
The regression tests cover canonical projection equivalence, transaction rollback and retry, duplicate completion, custom roles and competing workflow tasks. Repeated mixed-history measurements on MySQL and PostgreSQL and full Laravel 9–13 source qualification are recorded in the implementation PR.
Server 2.4.30 will ship this package update. Its image rebuild, publication and exact-image qualification are the next delivery step tracked on the owning issue.
Preserve UTC archive timestamps when loading workflow runs and summaries in applications using another timezone. Archive commands keep the correct ins
No database migration or worker protocol change is introduced by this patch.
Source qualification passed across MySQL, PostgreSQL and MariaDB, all five supported Laravel embedded-upgrade paths, static analysis, unit/coverage checks and dependency security audits.
Archive timestamp tracking: https://github.com/durable-workflow/workflow/issues/588
Workflow 2.2.19 makes schedule starts idempotent for the same nominal UTC occurrence. A normal tick, backfill, or buffered action now records a clean
Workflow 2.2.19 makes schedule starts idempotent for the same nominal UTC occurrence. A normal tick, backfill, or buffered action now records a clean already_fired_occurrence skip if that occurrence has already started. The migration indexes occurrence keys and backfills existing schedule history; during a rolling upgrade, new schedulers also recognize unindexed events written by older processes. The schedule correctness guide documents daylight-saving folds and gaps, manual triggers, and backfill boundaries.
This release also reads the retention details_pruned_at marker as a UTC instant, preserving the correct time in API consumers such as Waterline across application timezones and daylight-saving transitions.
Qualification covered the schedule boundary scenarios with published Workflow 2.2.18 on SQLite, MySQL, PostgreSQL, and MariaDB, then verified the candidate fix across those databases. The exact release commit passed the full database, Laravel upgrade, quality, regression, and coverage matrix. The published-package verification passed, including Laravel 9–13 upgrades. A fresh install of the exact published 2.2.19 package passed the schedule boundary cases on all four databases and the retention serialization probe with published Waterline 2.0.7 on PostgreSQL 17. Download the raw synthetic evidence.
Run the Workflow package migrations before restarting schedule processing. Server images pin their own Workflow package version and need a separate update and image qualification. The schedule implementation and raw evidence and retention fix provide the source review.
Workflow 2.2.18 keeps accepted external signal inputs bounded in durable command and history records. The command retains the immutable payload refere
Workflow 2.2.18 keeps accepted external signal inputs bounded in durable command and history records. The command retains the immutable payload reference, and both workflow worker paths store large applied signal values through the configured external storage policy. Replay resolves the original bytes and preserves declared argument order, defaults and variadic arguments.
The change is covered by an external Avro signal regression, a cold-replay corpus fixture, bridge and contract tests, and the full MySQL, PostgreSQL, MariaDB, unit coverage, quality and supported Laravel upgrade matrix. Published-package verification passed, including Packagist source identity, the platform contract and supported Laravel upgrades. Packagist resolves this release to commit 09158ab3fb4cfa5e46e320e2d70853122af209cc.
Server pins its own Workflow package version. The Server ingress change and published-image conformance are tracked in Server #262. The implementation PR contains the source qualification evidence.
Workflow 2.2.17 adds a bounded, single-event projection path for terminal WorkflowCompleted and WorkflowFailed events. Server can use it to refresh th
Workflow 2.2.17 adds a bounded, single-event projection path for terminal WorkflowCompleted and WorkflowFailed events. Server can use it to refresh the selected-run timeline after recording the authenticated worker command, without loading or rewriting the rest of a long run's history. This package release alone does not update Server's separately pinned image.
a2724ec07e043ae814dbe9a46f1890f8c4fd4bde, the published platform contract matches, and supported Laravel upgrade jobs passed.Server's follow-through is tracked in Server #257 and PR #258. It will pin this exact package and verify the customer-visible result against a published Server image.
Workflow 2.2.16 reduces long-history projection work in three paths:
Workflow 2.2.16 reduces long-history projection work in three paths:
The source matrix passed. In an isolated candidate-source PostgreSQL check of a 4,046-entry history, the rollback-only timestamp diagnostic found 413 redundant updates before and zero after. The broader Server #237 workload verified the exact workflow result and ordered history with published Server 2.4.21 and Python SDK 2.3.5, but used an unreleased Workflow source overlay for these fixes. This release does not update Server's separately pinned Workflow dependency.
The immutable tag points to source commit f91bd13856d9258dd04bafa90b9f6eb8d0b67cb7. Published-package verification passed: Packagist resolved 2.2.16 to this commit, the published platform contract matched, and all supported Laravel 9 through 13 upgrade jobs passed.
Workflow 2.2.15 avoids rewriting unchanged timeline JSON payloads during projection. MySQL's JSON key normalization previously made equivalent payload
Workflow 2.2.15 avoids rewriting unchanged timeline JSON payloads during projection. MySQL's JSON key normalization previously made equivalent payloads appear dirty, causing repeated SQL updates across long workflow histories. The regression verifies that an equivalent payload causes no update and a genuinely changed payload still persists.
The fix and candidate-source evidence passed the full Workflow test matrix. An isolated 4,000-signal Server workload with eight activities, eight timers and continue-as-new verified the exact result and ordered history. Its rollback-only 100-entry diagnostic dropped from 100 redundant updates to zero. Timing results from that workload are a single paired observation and are not a published capacity rating.
Published-package verification passed. Packagist resolved 2.2.15, the published platform contract matched, and all supported Laravel 9 through 13 upgrade jobs passed. The immutable tag points to source commit ff73cea8c93f72f2d67b7473e17ce028762baf3a.
This release does not update the separately pinned Workflow dependency in the Server image. Server #237 tracks the wider long-history qualification and image follow-through.
Workflow 2.2.14 fixes backend capability checks when workflows.storage.connection selects a supported SQL database and the Laravel application default
Workflow 2.2.14 fixes backend capability checks when workflows.storage.connection selects a supported SQL database and the Laravel application default selects a different, unsupported driver. The capability snapshot now follows the same Workflow storage connection used by the models and migrations. An explicit database connection argument still takes precedence.
The regression test and fix passed unit, MySQL feature, regression-corpus, and quality checks. Published-package verification passed, including the supported Laravel 9 through 13 upgrade matrix. Packagist resolves 2.2.14 to source commit 2f3509954fc1afc867a21820e8307d29c17c878f.
Standalone Server images pin their Workflow package separately. Server 2.4.21 embeds Workflow 2.2.13.
Workflow 2.2.13 keeps repeated buffered signal admission bounded when an open workflow task and a complete run-summary projection are available. It up
Workflow 2.2.13 keeps repeated buffered signal admission bounded when an open workflow task and a complete run-summary projection are available. It updates the history budget, task diagnostics, and timeline without loading every earlier command and history event. The existing full projection path still handles first signals, incomplete summaries, runtime-reserved signals, and custom projection roles that do not implement the optional interface.
In three paired local SQLite runs of 200 signals with the worker stopped, total admission CPU fell from 19.73–19.90 seconds to 2.42–2.43 seconds. Last-50 signal p95 fell from 174.71–175.90 ms to 12.86–13.11 ms. Every run retained 200 received events and 200 pending signals. The fixture and raw results record the commands, SQL calls, memory, and limits of this measurement.
The exact-head full matrix passed MySQL, PostgreSQL, MariaDB, Laravel upgrades, coverage, and replay regression. This patch does not change the SDK wire protocol. Server images pin their own Workflow version, so Server #237 tracks the published image update and long-history qualification.
Workflow 2.2.12 records when retained workflow-run details are removed by retention cleanup. The nullable WorkflowRun.details_pruned_at timestamp is s
Workflow 2.2.12 records when retained workflow-run details are removed by retention cleanup. The nullable WorkflowRun.details_pruned_at timestamp is set in the same transaction as detail deletion, including when applications use a configured run model and storage connection. A repeated cleanup preserves the original timestamp. Rejected or rolled-back cleanup leaves it unset.
The marker is a supported read contract for operator tools such as Waterline. Null does not prove that details remain present: old prunes and genuinely empty histories cannot be distinguished without an authoritative record, so this release does not infer or backfill timestamps. Terminal status and run identity remain intact. Applications with a custom workflow_runs table must add a nullable details_pruned_at timestamp with microsecond precision as described in the API stability guide.
This patch does not change the SDK wire protocol. Source qualification: full database and Laravel matrix, release identity PR. The published-package verification workflow runs from this exact tag.
Workflow 2.2.11 fixes an early durable timer wakeup in poll mode. If a queue transport delivers a timer job before its durable deadline, the runtime n
Workflow 2.2.11 fixes an early durable timer wakeup in poll mode. If a queue transport delivers a timer job before its durable deadline, the runtime now queues another bounded wakeup. This also covers timers whose transport delay is capped for long waits.
The patch keeps ordinary poll-mode workflow and activity tasks on external polling. It does not change the public SDK protocol.
Source qualification: full pre-merge matrix and main-branch matrix. Server #230 tracks the downstream Server image adoption and published-artifact worker-stop check.
This patch preserves an unambiguous UTC instant for new workflow history events and stores timeline and wait projection timestamps consistently in UTC
This patch preserves an unambiguous UTC instant for new workflow history events and stores timeline and wait projection timestamps consistently in UTC. It fixes repeated-hour ambiguity for new history during autumn clock changes and prevents non-UTC projection timestamps from drifting or repeatedly appearing stale. See #556 and #555.
The new nullable recorded_at_utc column is added to the default and existing configured history-event tables. New writers retain the legacy local recorded_at field for older readers; new readers prefer the UTC value. The migration does not rewrite existing history. Old local timestamps whose offset was never stored cannot be corrected without independent evidence. Applications that create or replace a custom history-event table in their own migrations must include the nullable UTC column before starting new writers. During a rolling upgrade, keep old and new workers on a consistent PHP timezone and finish upgrading writers before relying on repeated-hour correctness.
After upgrading all projection writers, back up the database and inspect workflow:v2:rebuild-projections --needs-rebuild --dry-run --json. Rebuild affected derived rows, then confirm a second dry run selects no unchanged runs. The rebuild leaves authoritative history unchanged and cannot infer a missing old offset. See the history timestamp guide and projection timestamp guide.
The source fixes passed full 20-job matrices for history and projections, including supported Laravel upgrades, database feature shards and coverage. This patch does not change the SDK wire protocol.
This patch prevents a schedule tick from acting on a due occurrence that became stale before it acquired the schedule row lock. The tick now rechecks
This patch prevents a schedule tick from acting on a due occurrence that became stale before it acquired the schedule row lock. The tick now rechecks the captured occurrence against the locked schedule's current next_fire_at at UTC microsecond precision. An obsolete occurrence returns skipped with reason stale_occurrence, without advancing the schedule, applying an overlap policy, buffering, cancelling, terminating, or starting another workflow. Manual triggers and explicit backfill keep their existing behavior.
This corrects #551. Regression coverage includes concurrent tick snapshots, a manual trigger between selection and locking, all overlap policies, a completed run using the built-in PHP-class starter, and offset/microsecond comparisons. The exact-head source matrix passed before the patch release.
There is no new migration or worker protocol change in 2.2.9. Applications upgrading from a version before 2.2.8 should still follow the existing UTC schedule timestamp migration guidance from 2.2.8.
Workflow 2.2.8 fixes schedule firing across the repeated local hour when clocks fall back, including the Europe/Kyiv case reported in #548. Absolute s
Workflow 2.2.8 fixes schedule firing across the repeated local hour when clocks fall back, including the Europe/Kyiv case reported in #548. Absolute schedule timestamps are stored and queried as UTC instants, so a schedule survives a database reload and a fresh PHP process without shifting to the second occurrence of a repeated local time. The same focused regression covers spring transitions and the scheduler's due query.
The upgrade migration converts legacy local schedule timestamps using the configured application timezone. For applications that wrote them in a different timezone, set DW_V2_LEGACY_SCHEDULE_STORAGE_TIMEZONE for the migration. A legacy timestamp in a repeated local hour does not encode which occurrence the old writer meant; the migration preserves the instant the old code would have hydrated and documents this limit.
This is a patch release for the embedded Laravel schedule path. The worker wire protocol is unchanged. Source matrix: 36254886844. Published-package verification and Laravel upgrade matrix: 36255854281. Changes: #549 and #550.
One column per quarter.