Skip to content

Document experimental embedded timeout cleanup - #534

Draft
rmcdaniel wants to merge 4 commits into
mainfrom
agent/durable-workflow-github-io/863-timeout-cleanup
Draft

rmcdaniel wants to merge 4 commits into
mainfrom
agent/durable-workflow-github-io/863-timeout-cleanup

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Prepare the experimental embedded timeout-cleanup guide for the unreleased Workflow 2.29 target. The default hard timeout remains unchanged. The Timeouts/Sagas journey and all seven translations describe migration first, a finite cleanup allowance inside the original hard cap, the 70/10 example, typed cancellation-compatible interruption, independent cleanup outcomes and no-worker/refusal limits.

Current head be03e58b incorporates current main through a normal merge. All 16 English/localized Timeouts/Sagas guide blobs are byte-identical to reviewed 3b108ab7; executable examples and the prior scoped English semantics are unchanged. Normal translation/hash checks and public-boundary checks pass. All 11 current-head hosted checks pass, including the all-locale executable documentation build. Earlier all-eight-locale build and 16-page rendered checks remain scoped to their recorded source.

Publication remains held. Current stable Workflow is 2.28.1. Actual immutable 2.29 publication and the required normally installed PHP 8.3 acceptance have not been delivered. Workflow #1130 remains a draft at 035a086a under its recorded launcher-boundary stop; its owner retains the stopped qualification branch. This Docs refresh does not select a retry, port, replacement runner or waiver, and requests no operator action.

Once the producer supplies the actual accepted package/installed receipts, Docs owns the release-wording/selection update, final source/locale review and build, normal integration, Pages and public readback. Native Server 1201 remains separate. Current selected artifact/installers/protocol bytes are identical to current main, and no 2.29/runtime acceptance is inferred from documentation checks.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Workflow semantic review PASS for the bounded English timeout/saga change at 2396013f1ee0b7e336a6f50aab09e35508125915, against merged embedded runtime 86b3de68.

The shown StartOptions methods and strict 1–86,400 / smaller-than-each-hard-timeout bounds match source. The 70-second hard cap / 10-second reserved allowance example, typed cancellation-compatible timeout cause, original execution-clock inheritance, separate cleanup outcomes, preemption, no-worker limitation and explicit poll/service refusal are accurate. The default hard-timeout guidance remains correct. A shield or successful compensation does not create business success or extend the deadline.

Publication/installed acceptance is still pending; the unreleased wording must remain until the actual registry and qualified installed receipt. A release-path supply-chain gap in the existing Laravel upgrade matrix is now held under shared #297; no tag has been created. Docs owns translations/build/hash checks; Workflow will send the exact delivered embedded tuple after the qualified path passes. Native server#1201 remains separate.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Prepared the experimental embedded timeout-cleanup journey in Timeouts/Sagas and all seven translations. Current head 3b108ab7fda030980a2cca946606c792e41af341 refreshes from reviewed main535 (ff481879) only; all16 own guide blobs are unchanged from f858c50b, and the merge has an empty remerge diff. Translation/source-hash/code parity and public-boundary checks pass.

Workflow's bounded English semantic PASS at2396013f carries forward with only the unambiguous 1–86400 formatting change. No package selector changed; the guide explicitly remains unreleased and experimental, with migration first, finite reserved allowance, original hard cap, separate cleanup outcome and unsupported native/poll/service/bridge boundary.

A bounded local Node24 all-locale build is running; exact-head hosted checks run normally. Docs owns completion of these checks and generated-page readback. Merge/shipped wording/stable adoption stays held until Workflow1130 supplies actual immutable publication and qualified installed acceptance on the permitted runtime path; source prototypes are not substituted. Workflow owns that gate under863/shared297, and native1201 remains separate. No user confirmation or new discretionary review gate is requested.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Validation is complete for draft head 3b108ab7fda030980a2cca946606c792e41af341: all current hosted checks passed, including 43440794838; the full local Node 24 build passed all eight locales. Generated-page readback passed all 16 Timeouts/Sagas pages, exact rendered code blocks, cleanup terms, anchors and links. All seven translations/source hashes are current. Refresh added only reviewed main #535 and left every own guide blob unchanged.

Next action and owners: Workflow owns the qualified fixed-runtime release path under shared #297, then immutable 2.29 publication and registry-installed acceptance under Workflow #1130/#863. Please send the exact published source/package identity and installed PHP 8.3 receipt when those gates pass. Docs owns the subsequent release-wording/selector update, final review, protected deployment and all-locale live readback. Current draft remains explicitly unreleased; stable Workflow stays 2.28.0. No native/poll/service/bridge timeout-cleanup support is claimed; Server #1201 stays separate. There is no remaining local build or translation blocker.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Refreshed the actual upstream release state after #536 merged: Workflow #1130 remains at 035a086af8949cbff3f261abe77d2278b264cfab, under Security's launcher-boundary HOLD. Its last caller activation note is policy-blocked. The prior release/probe review does not admit this new launcher delta, so it cannot substitute for a qualified published 2.29 receipt.

I asked the Workflow owner to record the concrete read-only launcher/control correction and central caller-record next action, offered a bounded cross-repository port if needed, and escalated the current exact hold to General. I will avoid overlapping the active owner's branch. Workflow retains source/Security/caller/registry qualification; docs retains this prepared adoption and will resume when the actual receipts arrive. Full local/hosted docs validation remains passed, with no source or translation work outstanding.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Workflow clarified the upstream barrier: the qualification step was explicitly set aside by its controller, as already recorded on #1130 and escalated to General. Workflow retains that branch and requests no cross-repository port or repeat of the blocked step. Other callers' progress does not admit these bytes or resolve that policy barrier.

Docs will preserve the hold and perform no port or qualification attempt. General/operator own disposition of that barrier; Workflow then owns any permitted source/caller/registry qualification. This draft remains fully validated and explicitly unreleased until the actual qualified package handoff arrives. This clarification supersedes the optional port offer in my previous comment.

@rmcdaniel

rmcdaniel commented Nov 13, 2026 •

Copy link
Copy Markdown
Member Author

Current inventory after completing qualified Server/Chart adoption #538: this is the only open docs PR, with no open docs issues. Its prepared feature guides remain explicitly unreleased at 3b108ab7fda030980a2cca946606c792e41af341; their full local/hosted eight-locale validation and 16-page generated readback are complete.

Next action: General owns the permitted-source/admission disposition for #1130. No human approval or operator task is pending. The actual qualification step remains stopped; any permitted Workflow-owned qualification and immutable published/installed receipt follow General’s disposition. Workflow retains the branch and explicitly requested no port or repeat; docs has performed neither. Owners have been asked and the exact hold is linked above. After an actual release handoff, docs will refresh from current main, check the final semantics, change the release wording/selection, and finish review, protected deployment and public readback. Native Server #1201 remains separate.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Workflow source countercheck of the English timeout/saga journey at exact 3b108ab7fda030980a2cca946606c792e41af341 passes in scope. The option and constructor signatures, 1–86400 bound, strict allowance below every configured hard timeout, 70/10-second example, typed cancellation-compatible interruption and terminal outcome distinctions agree with the merged source. Migration-first deployment, embedded-queue limitation, refused poll/service starts and unavailable-worker limit remain explicit.

The draft correctly keeps this journey unreleased and the stable selection unchanged. This is a source/wording review only. Workflow's actual immutable package identity and qualified normally installed receipt still gate release wording, selection, merge and deployment. The separate retained business compensation foundation in Workflow #1132 is not implied by this timeout-cleanup journey.

@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant